plan
/plan
Primary router for planning, architecture, and track management workflows. Analyzes user intent and dispatches to new-track, decompose, adr, tech-debt, change (and related). Use for starting features, breaking down work, recording decisions, managing debt, or handling scope changes.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 20.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Primary router for planning, architecture, and track management workflows. Analyzes user intent and dispatches to new-track, decompose, adr, tech-debt, change (and related). Use for starting features, breaking down work, recording decisions, managing debt, or handling scope changes.
Original author description
Primary router for planning, architecture, and track management workflows. Analyzes user intent and dispatches to new-track, decompose, adr, tech-debt, change (and related). Use for starting features, breaking down work, recording decisions, managing debt, or handling scope changes.
How it works
- When to Use
- Routing Logic
- Dispatch Examples
- Relationship to Primary Workflow
- Quality Gate
SKILL.md preview
--- name: plan description: "Primary router for planning, architecture, and track management workflows. Analyzes user intent and dispatches to new-track, decompose, adr, tech-debt, change (and related). Use for starting features, breaking down work, recording decisions, managing debt, or handling scope changes." --- # Plan - Planning & Architecture Router `/draft:plan` is the consolidated entry point for all planning and upfront architecture work in the Context-Driven Development lifecycle. ## When to Use - Starting a new feature, bug fix, or refactor track - Decomposing large modules or changes into dependency-aware units - Recording Architecture Decision Records (ADRs) - Cataloging and prioritizing technical debt - Handling mid-track requirement or scope changes ## Routing Logic The router parses intent from natural language and dispatches to the correct leaf skill. Ambiguous requests surface a short menu of options. | User Intent Keywords | Dispatches To | Purpose | |---------------------------------------|-----------------------|---------| | new feature, new track, start X, add Y, plan a refactor, fix the Z bug | `/draft:new-track` | Collaborative spec + plan creation for track | | decompose, break into modules, dependency map | `/draft:decompose` | Module decomposition + graph | | adr, architecture decision, record decision, design decision | `/draft:adr` | ADR authoring and evaluation | | tech debt, technical debt, catalog debt, debt analysis | `/draft:tech-debt` | 6-dimension debt scan + prioritization | | change, scope changed, requirements changed, update spec, mid-track pivot | `/draft:change` | Structured change impact & plan update | ## Dispatch Examples User: "start a new feature for user profile editing" → dispatches to `/draft:new-track "user profile editing"` User: "decompose the payment module" → dispatches to `/draft:decompose "payment module"` User: "document our decision to use event sourcing" → dispatches to `/draft:adr "Use event sourcing for order processing"` User: "find and prioritize our technical debt" → dispatches to `/draft:tech-debt` User: "the requirements changed, we need to support multi-tenancy now" → dispatches to `/draft:change "add multi-tenancy support"` ## Relationship to Primary Workflow `/draft:plan` augments but does not replace the core `/draft:new-track` and `/draft:implement` flow. Many planning activities are launched via `/draft:plan` for discoverability, then flow into the primary track lifecycle. Direct leaf commands remain available during the transition period (see MIGRATION). ## Quality Gate All planning dispatches should result in updated `draft/tracks/<id>/spec.md` or `plan.md` (or new ADR/debt artifacts) with proper metadata headers and citations back to product/tech-stack context.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · drafthq/draft | 100 | MIT |
| mlophez/polix-ai | 100 | Apache-2.0 |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| duronext/jig | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| xoai/sage | 100 | MIT |
| JoDi-27/JoDi-SDD | 100 | MIT |
Database snapshot: 13.11.2026 · package version b198b17966bc (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100manage-tech-debt
Track, categorize, and prioritize technical debt when the user asks to manage tech debt, create a tech debt register, assess code quality, or plan refactoring work - 100cto-advisor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Includes tech debt analyzer, team scaling calculator, engineering metrics frameworks, technology evaluation tools, and ADR templates. Use when assessing technical debt, scaling… - 100cto-advisor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Includes tech debt analyzer, team scaling calculator, engineering metrics frameworks, technology evaluation tools, and ADR templates. Use when assessing technical debt, scaling… - 90tech-debt-register
Track technical debt deliberately by framing each item as interest owed and budgeting steady paydown. Use when debt is piling up as vague complaints and you need to make it fundable work. - 90technical-debt-manager
Inventories technical debt, scores it by cost and risk, and builds a paydown plan that fits around feature work. Use when the codebase slows the team down, for refactoring priorities, or to justify cleanup time to stakeholders. - 100track-management
Use this skill when creating, managing, or working with Conductor" tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.