fa7e166f3e
- Add reminders page with navigation support - Upgrade BMad builder module to skills-based architecture - Refactor MCP server: extract tools and auth into separate modules - Add connections cache, custom AI provider support - Update prisma schema and generated client - Various UI/UX improvements and i18n updates - Add service worker for PWA support Made-with: Cursor
1.9 KiB
1.9 KiB
wipFile, deferred_work_file
| wipFile | deferred_work_file |
|---|---|
| {implementation_artifacts}/spec-wip.md | {implementation_artifacts}/deferred-work.md |
Step 2: Plan
RULES
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config
{communication_language} - No intermediate approvals.
INSTRUCTIONS
- Investigate codebase. Isolate deep exploration in sub-agents/tasks where available. To prevent context snowballing, instruct subagents to give you distilled summaries only.
- Read
./spec-template.mdfully. Fill it out based on the intent and investigation, and write the result to{wipFile}. - Self-review against READY FOR DEVELOPMENT standard.
- If intent gaps exist, do not fantasize, do not leave open questions, HALT and ask the human.
- Token count check (see SCOPE STANDARD). If spec exceeds 1600 tokens:
- Show user the token count.
- HALT and ask human:
[S] Split — carve off secondary goals|[K] Keep full spec — accept the risks - On S: Propose the split — name each secondary goal. Append deferred goals to
{deferred_work_file}. Rewrite the current spec to cover only the main goal — do not surgically carve sections out; regenerate the spec for the narrowed scope. Continue to checkpoint. - On K: Continue to checkpoint with full spec.
CHECKPOINT 1
Present summary. If token count exceeded 1600 and user chose [K], include the token count and explain why it may be a problem. HALT and ask human: [A] Approve | [E] Edit
- A: Rename
{wipFile}to{spec_file}, set statusready-for-dev. Everything inside<frozen-after-approval>is now locked — only the human can change it. Display the finalized spec path to the user as a CWD-relative path (no leading/) so it is clickable in the terminal. → Step 3. - E: Apply changes, then return to CHECKPOINT 1.
NEXT
Read fully and follow ./step-03-implement.md