Agentic plugin for structured project planning — lifecycle skills for research, specs, design, implementation, and review, with a generated artifcat tracking system.
Explore possibilities for a problem or opportunity with structured evaluation. Do NOT enter plan mode — this skill produces a brainstorm artifact directly. brainstorm, explore options, what are our options.
How to drive the sdd binary — artifact reads/writes, lifecycle transitions, evidence, validation, the decision ledger. Load whenever about to run sdd, record completion evidence, transition a task/phase/plan status, create or edit an SDD artifact, or query plans outside a lifecycle skill.
Record, look up, or reconcile entries in the decision ledger — the persistent log of decided truths. record decision, log this decision, what did we decide, decision ledger, supersede decision.
Recording user decisions as durable truth in the decision ledger. Load whenever the user makes a design or architecture choice, defines a project concept or term, answers a design question, reverses an earlier decision, or when current work touches a topic the ledger may already govern — including plain conversation…
Create a technical architecture and design document. Do NOT enter plan mode — this skill produces a design artifact directly. design this, architecture for, technical design.
Execute an approved spec-driven implementation plan phase, update task statuses, and verify code changes. Use when asked to implement an active plan or execute a specific phase or task.
Create or expand a structured implementation plan with phases, tasks, subtasks, and verification criteria. Re-running on an existing plan deepens it — adds tasks, fills gaps, refines subtasks. Do NOT enter plan mode — this skill produces plan artifacts directly. create a plan, plan this, implementation plan, expand…
Set up spec-driven planning in a repository by creating planning-config.json, artifact directories, ignore entries, and optional AGENTS.md guidance. Use when asked to initialize or configure planning for a repository or worktree.
Write a requirements specification for a feature. Do NOT enter plan mode — this skill produces a spec artifact directly. write spec, specify requirements, requirements for.
Explore possibilities for a problem or opportunity with structured evaluation. Do NOT enter plan mode — this skill produces a brainstorm artifact directly. Triggers: /brainstorm, brainstorm, explore options, what are our options.
Review implementation code against the plan for drift, gaps, and blind spots. Triggers: /code-review, review code, check implementation, compare to plan, code vs plan.
Record, look up, or reconcile entries in the decision ledger — the persistent log of decided truths. Triggers: /decide, record decision, log this decision, what did we decide, decision ledger, supersede decision.
Create a technical architecture and design document. Do NOT enter plan mode — this skill produces a design artifact directly. Triggers: /design, design this, architecture for, technical design.
Create or expand a structured implementation plan with phases, tasks, subtasks, and verification criteria. Re-running on an existing plan deepens it — adds tasks, fills gaps, refines subtasks. Do NOT enter plan mode — this skill produces plan artifacts directly. Triggers: /plan, create a plan, plan this…
Adversarial critical analysis of plans, specs, or designs. Triggers: /poke-holes, poke holes, find gaps, challenge this, what could go wrong, devil's advocate.
Set up a directory for sdd-planner — generates planning-config.json, bootstraps planning directories, creates launcher scripts. Triggers: /setup, setup repo, configure repo, setup worktree, initialize planner, bootstrap planner.
★not rated 2 5d agoA48 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: