Menú
Manage plan lifecycle — list plans, mark completed/abandoned, move between directories
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Create or manage Architecture Decision Records (ADRs) in docs/decisions/
Use this skill working with Ash Framework or any of its extensions. Always consult this when making any domain changes, features or fixes.
Record a development session summary in the project devlog
Run E2E browser tests via Tidewave browser_eval against the running Phoenix dev server
Inspect LiveView state (assigns, components) via Phoenix.LiveView.Debug in project_eval
Morning briefing — where we left off, what to work on today. Fast, compact report from canonical sources.
Basado en la clasificación ocupacional SOC
| name | plan-status |
| description | Manage plan lifecycle — list plans, mark completed/abandoned, move between directories |
| argument-hint | [list | complete | abandon | activate] [plan-name] |
| disable-model-invocation | true |
Manage the lifecycle of design docs and implementation plans in docs/plans/.
docs/plans/
├── active/ # Currently being implemented
├── completed/ # Successfully implemented (kept for reference)
├── backlog/ # Future work, not yet started
└── abandoned/ # Decided not to implement (with reason)
/plan-status or /plan-status listList all plans organized by status. For each plan show: filename, title (from first heading), and date.
/plan-status complete [name-fragment]Move a plan (and its paired design doc) from active/ to completed/.
active/ by name fragment (fuzzy match OK)-design.md and -plan.md if they exist as a pair/plan-status abandon [name-fragment]Move a plan from active/ to abandoned/.
> **Abandoned**: [reason] (YYYY-MM-DD) line at the top of the fileabandoned//plan-status activate [name-fragment]Move a plan from backlog/ to active/ (starting implementation).
/plan-status cleanupScan for any plan files still in the root docs/plans/ directory (not in a subdirectory) and interactively sort them into the correct lifecycle folder.
superpowers:writing-plans land in docs/plans/ root by default. This skill helps sort them.-design.md) and implementation plans (-plan.md) are always moved together as a pair.backlog/ directory uses backlog-*.md naming (no date prefix) since timing is unknown.