Menu
This skill should be used when the user asks to "plan feature", "design feature", or wants to plan and design a new feature before implementation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Inspect drift between code, shared workflow references, and Claude, Codex, or Antigravity harness assets after architecture or workflow changes.
This skill should be used when the user asks to "sync guidelines", "document inspection", "check skill updates", "update project-dna", "sync patterns", "verify code-document consistency", or after architecture changes to verify Skills/AGENTS.md/CLAUDE.md match the actual code.
Guide a feature from requirements interview through architecture analysis, security check, and task decomposition.
Audit a domain or the full repository for architecture compliance using the shared architecture checklist and repository rules.
Review a pull request or local diff against the repository's shared Review Protocol (correctness, regression, stability, contract, architecture, security, governance).
Review a domain, file, or the full repository for OWASP-oriented security issues using the shared security checklist.
| name | plan-feature |
| argument-hint | feature description |
| description | This skill should be used when the user asks to "plan feature", "design feature", or wants to plan and design a new feature before implementation. |
Description: $ARGUMENTS
.claude/rules/architecture-conventions.md -- confirm current DO/DON'T rules.claude/rules/project-status.md -- confirm work currently in progress.claude/rules/project-overview.md -- confirm tech stack and structuresrc/*/ and exclude _core, _apps prefixesframing (Phase 0) + approach options (Phase 1) + plan (Phases 2~4)/execute-plan, which advances the ledger to executing (clearing the plan→execute block) and routes to the implement skills (/new-domain, /add-api, /add-cross-domain, etc.) internally. To run a single implement skill or self-evident follow-up directly, prefix the next prompt with a [trivial]/[hotfix] token (the block honours plan-waiver tokens) — invoking an implement skill while the stage is still planned without a token is hard-blocked. Never auto-continue from planning into implementation in the same turn (ADR 054)/plan-feature recursively. Implement skills must not call /plan-feature (planning happens before implement).agents/state/current-work.json via:
from work_ledger import update_goal_scope_plan, update_workflow_state
update_goal_scope_plan(goal="<one-line goal>", scope="<domains/files>", plan="<task list>", updated_by="skill:plan-feature")
update_workflow_state(stage="planned", plan_ref="<issue, PR, or plan file>", tasks=[{"id": "1", "title": "<task>", "status": "pending"}], updated_by="skill:plan-feature")
Read docs/ai/shared/skills/plan-feature.md for detailed steps and output format.
Also refer to docs/ai/shared/planning-checklists.md for question bank and templates.
For complex, architecture-changing, governor-changing, or multi-task work, hand
the approved Execution Packet to /execute-plan as a separate step — do not
implement within /plan-feature. Stopping at the packet is mandatory (ADR 054).