Loading...
Loading...
Found 107 Skills
Required methodology for planning, ideating, and delivering features or tasks. Use when user asks to "plan", "break down", "continue", or "figure out steps".
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
Insert urgent work as a decimal phase between existing phases, adding mid-milestone work, or creating intermediate phases. Triggers include "insert phase", "add urgent phase", "create decimal phase", "insert between phases", and "urgent work".
Define the framing of a problem. Change the statement, change the solution space. Use when starting work, when solutions feel wrong, or when you suspect an X-Y problem.
Set aligned, measurable OKRs/goals and produce an OKR & Goals Pack (objectives, key results, anti-gaming guardrails, systems/habits, review cadence, grading plan).
Prioritize a product roadmap/backlog and produce a Roadmap Prioritization Pack (season framing, scoring model, ranked opportunities, roadmap, decision narrative, rollout plan).
When a user asks how long a task will take, requests a time estimate, or before starting any non-trivial coding task, immediately run scripts/estimate_task.py to analyze the codebase scope and provide a data-driven time estimate. Show the estimate breakdown, risk factors, and checkpoint recommendations without asking.
Generate multiple viable solution options after research is complete, before converging on a single approach. Use when you need to explore the solution space, ask clarifying questions, and produce 3-5 distinct options to consider.
Use when planning work (to create items and tasks), when starting implementation (to mark tasks in-progress), when completing work (to mark tasks done), or to check backlog status. Manages .backlogmd/ for features, bugfixes, refactors, and chores.
Synthesizes research findings into design decisions via codebase investigation. Use when (1) translating research into implementation approaches, (2) selecting between design alternatives, (3) executing after /research or deep-research, or (4) preparing input for /plan phase.
Break down a requirement that is "too large to be implemented as a single feature" into a list of sub-features with dependencies and statuses, and place it in the independent `codestable/roadmap/{slug}/` directory — serving as the seed and scheduling basis for subsequent multiple feature processes. Two modes: new (draft a new roadmap from a large requirement), update (refresh an existing roadmap: add items, modify dependencies, reorder, mark as drop). Division of labor with requirements / architecture — those two record "what the system is now", while the roadmap records "what we plan to do next". Trigger scenarios: Users say "I want an X system", "Help me break down this requirement", "Schedule this large requirement", "Create a roadmap", or it is found during the feature-design phase that the requirement is too large to fit into a single feature.
Generate a phase-based task breakdown in tasks.md from spec.md and plan.md