ks-architect
01Command Claude Code
Set the technical HOW — stack, patterns, conventions, design.
Command Claude Code
Set the technical HOW — stack, patterns, conventions, design.
Command Claude Code
Capture and structure the global design system into docs/design-system.md. Doesn't generate visuals — it records them.
Command Claude Code
Derive a story's screen from the design system. Autonomous path (the agent produces it) or brief path (an external tool produces it and the result comes back). Never freestyles outside the system.
Command Claude Code
Get a story implemented in an isolated subagent. Never codes in the main context.
Command Claude Code
Affiche le pipeline killer-saas — l'ordre des phases et la règle unique.
Command Claude Code
Chain a story's full cycle — Research → Design → Plan → Execute → Review → Ship — with two blocking human checkpoints (plan validation, ship confirmation).
Command Claude Code
Break a story into sequenced tasks, ready to execute.
Command Claude Code
Frame the kill — target SaaS, kill mode, perimeter, the WHAT and the WHY.
Command Claude Code
Explore a story's real context before planning — current code, APIs, traps.
Command Claude Code
Get a story reviewed by a fresh-context subagent. Gate before Ship. Never reviews in the context that wrote the code.
Command Claude Code
Ship the story per the project's Merge mode and Ship confirmation (AGENTS.local.md).
Command Claude Code
Show the project's pipeline state — framing docs, per-story progress, next command.
Command Claude Code
Review the story breakdown against the PRD perimeter, in a fresh-context subagent. Cheapest place to catch a bad split.
Command Claude Code
Break the PRD down into shippable, agentic-ready user stories.
Command Claude Code
Create the project's AGENTS.local.md — the settings and commands the pipeline reads. Runs once, before /ks-prd.
Command Claude Code
One small story, end to end, in three contexts instead of six — research and plan fused, same implementer, same fresh-context review, same gates.
Command Claude Code
Work that is not a product feature — documentation, content, test cleanup, tooling — with a short validated plan, the implementer, and a verification sized to what changes.
Command Claude Code
Audit an existing end-to-end suite against the testing doctrine, then prune it — keep, rewrite or delete each spec, after a human validates the list.
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: