Loading...
Loading...
Found 31 Skills
Complete project planning and execution framework. Automatically includes all 14 planning sections (planning/0-Master-Index.md through planning/13-Lessons-Learned-Continuous-Improvement.md) plus all 9 Claude Skills (tech-stack-selector, architecture-decisions, code-standards-enforcer, ci-cd-pipeline-builder, agile-executor, project-risk-identifier, automation-orchestrator, webapp-testing, web-artifacts-builder). When installed, all planning templates and execution skills are immediately available.
This skill is activated when the user's team faces execution problems—such as failing to meet OKRs, constantly changing plans, and passive team response to instructions. Typical trigger signals: Goals are set but execution deviates, plans can't keep up with changes, and the team only completes assigned tasks without proactive thinking. Non-trigger scenarios: Execution is good and only needs fine-tuning, the problem lies at the strategic level rather than the execution level, and individual work does not require a team execution framework. Difference from the "Strategy-Tactics Dialectics" skill: This skill solves "how to balance the three dimensions of execution" (execution layer), while the latter solves "dialectical design of offensive and defensive levels" (strategy layer).
Create and manage persistent markdown planning files for structured task execution. Use when the user asks to "create a plan", "track progress", "start a research project", or when a task requires more than 5 tool calls and needs structured phase tracking to stay focused and avoid goal drift.
Plan and lead execution when outcomes are uncertain and requirements are ambiguous. Produces an Uncertainty Planning Pack (uncertainty map, hypotheses + experiments, buffers + triggers, cadence + comms). Use for ambiguity, unknowns, hypothesis-driven planning, experimentation, contingency planning.
Implement a plan or feature. Use when the user has a defined plan ready to be coded.
Use this when you have a written implementation plan to execute in a separate session with review checkpoints.
Under genuine uncertainty with no reliable forecast, inventory means, cap downside at affordable loss, act for commitments, and let goals emerge from controllable moves.
Implement an already-decided bounded scope from a Plan, handoff, review findings, direct brief, docs task, fix, or refactor. Use for implementation or continuation work; use diagnose-issue first when the cause is unknown.
Generate phased, dependency-ordered tasks from specs. Identifies parallelization opportunities. task planning, dependency ordering, phased breakdown, parallel tasks Use when: converting specifications to implementation tasks DO NOT use when: writing specs - use spec-writing. Not for execution - use speckit-implement.
Build your MVP following the AGENTS.md plan. Use when the user wants to start building, implement features, or says "build my MVP", "start coding", or "implement the project".
For questionable requests, clarify with context before implementing
Break an implementation plan markdown file into a sequenced, dependency-annotated, checkbox-tracked task list saved as a sibling doc (e.g. `docs/<feature>-tasks.md`). Each task is annotated with the lower-numbered tasks it depends on (or marked dependency-free) and ordered topologically, so independent tasks can be implemented in parallel. The task list is the execution contract — each task is one logical commit that bundles the code change **and** the ticked checkbox together (never a separate "tick-only" commit). Use this whenever the user has an implementation plan (file like `docs/<thing>-plan.md`, an `## Implementation plan` section, or a freshly written design doc) and wants a step-by-step todo list to drive the build. Trigger on phrases like "break this plan into tasks", "make a task list", "generate the tasks doc", "turn this plan into checkboxes", "split this into steps I can implement one by one", or whenever a plan exists and the next move is execution — even if the user doesn't explicitly say "task list".