genkovich

genkovich/sdd

Plugin Claude Code

Plugin marketplace listing 1 plugin: sdd.

genkovich/sdd

Plugin Claude Code

Spec-Driven Development for Claude Code: 22 atomic, stack-agnostic skills + 11 subagents that carry a feature from idea → spec → ux-flows → design → data-model → API → screens → tasks → tests → implement → review → ship, plus a TDD implementation engine and a living decomposition roadmap above the per-feature flow.…

genkovich/sdd

Agent

Clean-context multi-perspective reviewer of an SDD feature's candidate approaches. Use during specify's ideation pass (hard depth) to pressure-test the three strategic approaches from three lenses — Engineer, Executive, UX — so the recommendation isn't blind to cost, feasibility, or the user. Read-only; returns one…

genkovich/sdd

Agent

Clean-context coherence critic for SDD artifacts (a spec or a SAD). Use after a Socratic pass to detect cross-section drift, coherence damage from user edits, structural gaps, and constraint/ quality leaks the per-section walk could not see. Read-only; reads the upstream artifacts itself; emits cited findings only. It…

genkovich/sdd

Agent

Clean-context adversary for SDD. Two modes, named by the dispatch prompt. (A) Ambiguity hunt over a written spec — used by clarify to find where two competent engineers would reasonably build different things (vague terms, unmeasured NFRs, under-specified ACs, conflicts). (B) Failure-mode hunt over a raw idea +…

genkovich/sdd

Agent

Read-only brownfield scout for SDD. Use when a skill (design, data-model) needs the existing codebase mapped before it designs against it — module boundaries, the patterns already in use, where similar features live, the migration/test conventions — or when fix needs a reported symptom localized to its code path.…

genkovich/sdd

Agent

Makes a failing SDD test pass — the GREEN + REFACTOR + GATE steps of test-driven development. Use after test-author has produced a red test for a task. Given the task and its quoted failing line, it writes the minimal production code to pass, refactors while staying green, and runs the per-task gate (unit +…

genkovich/sdd

Agent

Pencil-library keeper for the design canon. Use from design-system (tool: pencil) to reconcile the repo's .pen library with the canon: verify the app's ACTIVE document is the canon's penfile, seed the document variables from the token source (light + dark where the source has both), and ensure a foundations frame with…

genkovich/sdd

Agent

Clean-context competitive + adjacent-solution researcher for an SDD feature idea. Use during specify's ideation pass (medium/hard depth) to find how the market and adjacent products already solve this problem — so the spec's recommendation is grounded in what exists, not a guess. Has web access (WebSearch/WebFetch)…

genkovich/sdd

Agent

Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…

genkovich/sdd

Agent

Clean-context product decomposer. Use from the roadmap skill to break a product idea (idea-brief / PRD / vision note) into incremental, buildable steps with an explicit dependency graph and an execution path (waves of steps that can safely run in parallel). Read-only; returns one ready-to-review roadmap draft in the…

genkovich/sdd

Agent

Clean-context generator of the three strategic approaches for an SDD feature idea. Use during specify's ideation pass (hard depth) to lay out genuinely different ways to solve the problem — Simplicity (shortest path), Differentiation (the moat/wow), Balanced (the trade-off) — so the spec picks an approach from real…

genkovich/sdd

Agent

Writes the failing test FIRST for an SDD task — the RED step of test-driven development. Use when the implement engine needs a test that encodes a task's acceptance criteria before any production code exists. Given a task (title, acceptance-criteria text, definition of done, files hint), it writes the test(s) where…

genkovich/sdd

Skill Claude CodeCodex

Use to derive the API contract for a feature — an OpenAPI 3.1 document at docs/features/{slug}/contracts/openapi.yaml plus a drift/sync report (and an events doc when the feature has async flows). Triggers on "api for {slug}", "openapi for {slug}", "API contract for {slug}", "lock the interface for {slug}", "events…

genkovich/sdd

Skill Claude CodeCodex

Use to run an ambiguity sweep over a written spec.md and close every under-specified point before planning or design proceeds — so two engineers can't reasonably build different things from the same spec. Triggers on "clarify {slug}", "find ambiguities in {slug}", "is the spec ready", "sharpen the spec", "/sdd:clarify…

genkovich/sdd

Skill Claude CodeCodex

Use to classify a feature into XS/S/M/L/XL and write docs/features/{slug}/.size plus the pipeline route docs/features/{slug}/.route (quick|standard|full) so later skills know how much of each artifact to produce and how handoffs resolve skips. Triggers on "classify size", "feature size", "is this XS or M for {slug}"…

genkovich/sdd

Skill Claude CodeCodex

Use to design the data model AND generate the actual forward + rollback migrations in one pass — shippable SQL, not a plan. Triggers on "data model for {slug}", "schema for {slug}", "generate migrations for {slug}", "DB design + migration", "/sdd:data-model {slug}", "модель даних для {slug}", "схема для {slug}"…

genkovich/sdd

Skill Claude CodeCodex

Use to record a post-hoc or asynchronous architecture decision as a MADR ADR when it was NOT captured during the synchronous design pass — a choice made in code, in a chat, on a whiteboard, or one a tasks/review gate flagged as missing. Triggers on "ADR for {decision}", "adr for {slug}", "document the decision on…

genkovich/sdd

Skill Claude CodeCodex

Use to establish the project's design canon — docs/design-system.md: the design-tool choice (Figma MCP / Pencil MCP / code-only markdown), the platform posture (mobile-first / desktop-first / responsive), the token source, and the reusable component inventory. Once per repo, like survey. Triggers on "set up the design…

genkovich/sdd

Skill Claude CodeCodex

Use to produce a Software Architecture Document for a feature — Arc42 12 sections + C4 L1/L2 inline + ADRs spawned on a blast-radius gate — once spec.md exists. Triggers on "design {slug}", "architecture for {slug}", "SAD for {slug}", "arc42 for {slug}", "C4 context+container for {slug}", "/sdd:design {slug}"…

genkovich/sdd

Skill Claude CodeCodex

Use to fix a reported bug spec-first: reproduce it, trace the symptom to the owning feature's acceptance criteria, pin it with a failing (RED) test, apply the minimal GREEN fix through the same per-task gate implement uses, then patch the spec so the bug class can't silently return. Triggers on "fix {bug}", "fix the…

genkovich/sdd

Skill Claude CodeCodex

Use to capture or update domain terms in CONTEXT.md before their meaning drifts — whenever a fuzzy word shows up in an interview, spec, or review and you want one canonical definition plus a NOT-reference so a homonym can't bite you in six months. Triggers on "add term {X}", "what is {X} in our domain", "add to…

genkovich/sdd

Skill Claude CodeCodex

Use to implement a feature from its tasks.json with test-driven development — writes a failing test first, makes it pass, refactors, gates, and commits per task. Triggers on "implement {slug}", "build {slug}", "TDD {slug}", "code up the tasks for {slug}", "/sdd:implement {slug}", "імплементуй {slug}", "реалізуй фічу…

genkovich/sdd

Skill Claude CodeCodex

Use BEFORE specify to stress-test a raw idea — pressure-test it before you commit to a spec. A Socratic interview that surfaces hidden assumptions, names tradeoffs, exposes imprecisions, and proposes fresh angles. Scope is any idea (product, content, business, architecture, refactor approach), but in an SDD repo the…