MikeCodeur/killer-saas

85Stars on the repository
28Mods indexed here, across every type
16d agoLast push, which is what freshness is scored on
noneNo LICENSE: all rights reserved, so bodies are not copied

ks-architect

01

MikeCodeur/killer-saas

Command Claude Code

Set the technical HOW — stack, patterns, conventions, design.

not rated 85 +4 changed 1mo ago A 12 tokens

ks-design-system

02

MikeCodeur/killer-saas

Command Claude Code

Capture and structure the global design system into docs/design-system.md. Doesn't generate visuals — it records them.

not rated 85 +4 changed 1mo ago A 21 tokens

ks-design

03

MikeCodeur/killer-saas

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.

not rated 85 +4 changed 1mo ago A 42 tokens

ks-execute

04

MikeCodeur/killer-saas

Command Claude Code

Get a story implemented in an isolated subagent. Never codes in the main context.

not rated 85 +4 changed 1mo ago A 17 tokens

ks-help

05

MikeCodeur/killer-saas

Command Claude Code

Affiche le pipeline killer-saas — l'ordre des phases et la règle unique.

not rated 85 +4 changed 16d ago A 16 tokens

ks-orchestrator

06

MikeCodeur/killer-saas

Command Claude Code

Chain a story's full cycle — Research → Design → Plan → Execute → Review → Ship — with two blocking human checkpoints (plan validation, ship confirmation).

not rated 85 +4 changed 1mo ago A 31 tokens

ks-plan

07

MikeCodeur/killer-saas

Command Claude Code

Break a story into sequenced tasks, ready to execute.

not rated 85 +4 changed 1mo ago A 11 tokens

ks-prd

08

MikeCodeur/killer-saas

Command Claude Code

Frame the kill — target SaaS, kill mode, perimeter, the WHAT and the WHY.

not rated 85 +4 changed 1mo ago A 18 tokens

ks-research

09

MikeCodeur/killer-saas

Command Claude Code

Explore a story's real context before planning — current code, APIs, traps.

not rated 85 +4 changed 1mo ago A 15 tokens

ks-review

10

MikeCodeur/killer-saas

Command Claude Code

Get a story reviewed by a fresh-context subagent. Gate before Ship. Never reviews in the context that wrote the code.

not rated 85 +4 changed 1mo ago A 25 tokens

ks-ship

11

MikeCodeur/killer-saas

Command Claude Code

Ship the story per the project's Merge mode and Ship confirmation (AGENTS.local.md).

not rated 85 +4 changed 16d ago A 17 tokens

ks-status

12

MikeCodeur/killer-saas

Command Claude Code

Show the project's pipeline state — framing docs, per-story progress, next command.

not rated 85 +4 changed 1mo ago A 15 tokens

ks-stories-review

13

MikeCodeur/killer-saas

Command Claude Code

Review the story breakdown against the PRD perimeter, in a fresh-context subagent. Cheapest place to catch a bad split.

not rated 85 +4 16d ago A 25 tokens

ks-stories

14

MikeCodeur/killer-saas

Command Claude Code

Break the PRD down into shippable, agentic-ready user stories.

not rated 85 +4 16d ago A 15 tokens

ks-setup

15

MikeCodeur/killer-saas

Command Claude Code

Create the project's AGENTS.local.md — the settings and commands the pipeline reads. Runs once, before /ks-prd.

not rated 85 +4 changed 16d ago A 25 tokens

ks-flow

16

MikeCodeur/killer-saas

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.

not rated 85 +4 16d ago A 31 tokens

ks-chore

17

MikeCodeur/killer-saas

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.

not rated 85 +4 16d ago A 34 tokens

ks-test-prune

18

MikeCodeur/killer-saas

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.

not rated 85 +4 16d ago A 30 tokens

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: