| name | plan |
| description | Research the codebase and create an implementation plan following Propose/Justify/Recommend. Use this before any feature, fix, or refactor. |
| disable-model-invocation | true |
| allowed-tools | Read, Glob, Grep, WebSearch, WebFetch, Edit, Write, Task, EnterPlanMode, ExitPlanMode, AskUserQuestion |
Plan
You are planning a feature for Cortex TMS. Enter plan mode immediately.
Rules
- Enter plan mode — use EnterPlanMode before doing anything else
- Research first — read relevant source files, tests, docs, and patterns before proposing anything
- Follow Propose/Justify/Recommend:
- Propose: What you will build and how
- Justify: Why this approach, with evidence from the codebase
- Recommend: One clear recommendation — then stop and wait
- Write the plan — update NEXT-TASKS.md with a sprint checklist (- [ ] items) and acceptance criteria
- Update task files if needed:
- Move tasks between NEXT-TASKS.md and FUTURE-ENHANCEMENTS.md
- Update status markers in FUTURE-ENHANCEMENTS.md
- Archive completed sprints to docs/archive/
- Exit plan mode — present the plan for user approval via ExitPlanMode
- STOP — do not write any code. Wait for the user to approve or give feedback.
You CANNOT
- Touch any file in src/, bin/, templates/
- Edit README.md, package.json, or any config file
- Write code, tests, or build artifacts
- Run build, test, or lint commands
- Proceed to implementation without explicit user approval
Arguments
$ARGUMENTS