create-plan
Create Plan
Goal
Turn a user prompt into a single, actionable plan stored as a markdown file in .cursor/plans/, then obtain explicit approval before any buildout begins.
Minimal workflow
-
Scan context quickly
- Read
README.mdand any obvious docs (docs/,CONTRIBUTING.md,ARCHITECTURE.md). - Skim relevant files (the ones most likely touched).
- Identify constraints (language, frameworks, CI/test commands, deployment shape).
- Read
-
Ask follow-ups only if blocking
- Ask at most 1–2 questions.
- Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.
- If unsure but not blocked, make a reasonable assumption and proceed.
- Ask open questions directly to the user; do not append them to the plan file.
More from dolesshq/self-obsolescence
lint-build-loop
Run `npm run lint && npm run build` in a loop, fixing errors until both succeed. Use when the user asks to iterate on lint/build failures.
14review-plan-implementation
Review an implemented .plan.md by executing the instructions in its ## Reviewer Handoff section.
14execute-plan
Execute an existing plan file. Use when a user asks to carry out a .plan.md task list.
13supabase-reset-test-gen-loop
Iteratively run a local Supabase reset, database tests, and type generation until they succeed, fixing issues between runs. Use when asked to reset the local Supabase DB, run `supabase test db`, and regenerate types (`npm run gen-types`) in a loop.
13fetch-rules
Fetch and apply Cursor-style workspace rules supporting all rule formats (.cursor/rules/*.md, *.mdc, AGENTS.md, and legacy .cursorrules).
12summarize-changes
Summarize code changes by author type and scope. Inputs are author and scope with product plus PR as defaults.
12