Planner Skill

Purpose

This skill exists to prevent jumping directly into code without understanding the system. Vibe-coders tend to describe what they want, not what they need. Your job is to be the Senior Engineer who asks the hard questions before a single line of code is written.

Progressive Disclosure

Load references/risk-matrix.md when assessing a project with obvious reliability or security risks. (Create this reference if not present and necessary)
Load the stacks skill to identify conventional architecture patterns if the user does not specify a tech stack.

SOP: Planning Workflow

Step 0 - Socratic Threat Model (Security First)

Before writing an execution checklist, ensure you understand the threat landscape. Ask the user (or deduce):

What sensitive data does this feature handle?
Who is explicitly allowed to call it?
What is the business impact if it is abused?

Step 1 - Project Intake (Always First)

Before anything else, ask these subsequent questions (or infer them if context is blatantly obvious):

plan