--- title: "wiki-sdd" description: "Wiki-native spec-driven development loop for the llm-wiki agent wiki: bootstrap a project scope, grill intent into a glossary, synthesize PRDs and user stories, triage stories through a state machine, slice into tracker " canonical: https://agentpluginsdirectory.com/plugins/wiki-sdd last-updated: 2026-10-21 --- # wiki-sdd Wiki-native spec-driven development loop for the llm-wiki agent wiki: bootstrap a project scope, grill intent into a glossary, synthesize PRDs and user stories, triage stories through a state machine, slice into tracker issues, and implement slices via red-green-refactor TDD. - Slug: wiki-sdd - Publisher: Angel Bartolli - Repository: https://github.com/bartolli/kmd - Manifest: plugins/src/wiki-sdd/plugin.json - Version: 0.21.2 - License: MIT - Category (editorial): productivity - Skills: 10 (handoff, intent, retro, signal-dense, tdd, to-issues, to-stories, to-triggers, triage, wiki) - MCP servers: 1 (wiki) - Stars: 7 - Repository created: 2026-06-21 - Repository last pushed: 2026-09-05 - Publisher type: User - Listing: https://agentpluginsdirectory.com/plugins/wiki-sdd - Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json ## What wiki-sdd does, in the publisher's words Wiki-native spec-driven development loop for the ~/llm-wiki agent wiki, packaged as an Agent Plugins 1.0.0 plugin: plugin.json, the skills under skills/, the wiki MCP server in mcp.json, and the launcher it runs. A conformant client, Kiro today, installs this folder as is. Claude Code, Codex, and Cortex Code take rendered adapters of the same source (plugins/claude, plugins/codex, and the repo-root Cortex manifest). Arc: /intent → /to-stories → /triage → /to-issues → /tdd → /retro whenever drift is suspected → /handoff to close. signal-dense and /to-triggers sit outside the arc: invoke signal-dense before authoring specs, ADRs, and blueprints so wiki artifacts are written in canonical vocabulary rather than drafted loose from memory; invoke /to-triggers whenever a rule should become a gate, it interviews intent, authors the matching, and writes vault.yaml only after a dry-run proves fire and near-miss behavior. From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/bartolli/kmd/HEAD/plugins/src/wiki-sdd/README.md ## Skills - handoff: This skill should be used to close a session so the next one starts cold from corrected truth. Operator-invoked, gated on a retro note newer than the scope's last edit. Rewrites the primer within its budget first, then runs the status sweep (fully-resolved stories proposed for archiving, flipped on… - intent: Interview-style grilling that captures intent, sharpens vocabulary, and scaffolds wiki structure for a project scope. Use when the user wants to start a new workstream, refine an existing scope's intent, stress-test a plan against the project's domain language, or write a `glossary.md` (terms + rel… - retro: This skill should be used for a session retrospective at any point in a session, mid-session when drift is suspected, after a bug-hunting detour, after compaction, before a release cut, and always before /handoff. Asks three questions: 'What are you least confident about?', 'What's the biggest th… - signal-dense: Canonical-vocabulary mode for agentic threads where assistant output re-enters context. Composable register predicates (technical, affect, safety, beginner) bind rule application; canonical handles, typed entities, and direct predicates extend an implicit KG across turns. Trigger on "signal-dense",… - tdd: Implement a single `ready-for-agent` slice from a wiki user story using disciplined red-green-refactor with vertical tracer bullets. Reads the slice description, the story's Gherkin scenarios (as the test specification), `glossary.md` (for vocabulary), and the referenced specs/ADRs. Refuses horizon… - to-issues: Break a wiki user story into vertical-slice tracer-bullet checkboxes (or refine existing slices), and in `github`/`gitlab` mode mirror `ready-for-agent` slices to the remote issue tracker with wikilinks back to the story file. Operates on `kind: story` files in the wiki. Quizzes the user on slice g… - to-stories: This skill should be used to write wiki stories, Gherkin scenarios plus a first slice list, from either input: the current conversation, synthesized into a thin `plan/plan-{name}.md` with one `plan/{name}/story-N-{slug}.md` per story; or a promoted intent, elaborated into one story under the acti… - to-triggers: Turn a plain-language rule into a well-formed vault trigger entry. Interviews intent (remind vs warn vs block), then authors the matching mechanics itself, stemmed keyword choice, anchored regexes, glob semantics, predicate selection, proves fire and near-miss behavior with a dry run, and writes… - triage: This skill should be used to move intents and user-story files through the wiki's triage state machine. Intents (`draft` → `active` / archived with `promoted_to`, `dismissed`, or `fixed_by`) are triaged first, ordered by sightings; stories move `needs-triage` → `needs-info` / `ready-for-agent` / `r… - wiki: Bootstrap an existing project (not yet on the wiki) to use the `~/llm-wiki` Obsidian-based agent wiki. Scaffolds a new vault when none exists (vault.yaml, served templates, domain dirs). Writes three sections to the project instructions from a bundled template, `## First read`, `## Wiki integratio… Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized. ## MCP servers - wiki: transport: stdio; command: node ${PLUGIN_ROOT}/scripts/run-kmd.mjs mcp Read from the plugin's own mcp.json. Environment variable names only, never values.