Claude Skills by kp-multiverse

The per-feature workflow. Use when starting any feature, change, or fix: "build F003", "next feature", "add X", "fix Y". Chores build straight through; features run GRILL -> RED -> GREEN -> REVIEW -> MERGE with caps.

The security trigger and review procedure for this project. Use when deciding whether work needs a security pass, and to run one -- "does this need security review?", auth changes, new input surfaces, new tools.

On-demand debt sweep. Use when the owner asks for a cleanup pass, before a release or milestone, or when the codebase feels heavier than its feature count justifies.

The per-feature workflow. Use when starting any feature, change, or fix: "build F003", "next feature", "add X", "fix Y". Chores build straight through; features run GRILL -> RED -> GREEN -> REVIEW -> MERGE with caps.

The security trigger and review procedure for this project. Use when deciding whether work needs a security pass, and to run one -- "does this need security review?", auth changes, new input surfaces, new tools.

On-demand debt sweep. Use when the owner asks for a cleanup pass, before a release or milestone, or when the codebase feels heavier than its feature count justifies.

The per-feature workflow. Use when starting any feature, change, or fix: "build F003", "next feature", "add X", "fix Y". Chores build straight through; features run GRILL -> RED -> GREEN -> REVIEW -> MERGE with caps.

The security trigger and review procedure for this project. Use when deciding whether work needs a security pass, and to run one -- "does this need security review?", auth changes, new input surfaces, new tools.

On-demand debt sweep. Use when the owner asks for a cleanup pass, before a release or milestone, or when the codebase feels heavier than its feature count justifies.

The per-feature workflow. Use when starting any feature, change, or fix: "build F003", "next feature", "add X", "fix Y". Chores build straight through; features run GRILL -> RED -> GREEN -> REVIEW -> MERGE with caps.

The security trigger and review procedure for this project. Use when deciding whether work needs a security pass, and to run one -- "does this need security review?", auth changes, new input surfaces, new tools.

On-demand debt sweep. Use when the owner asks for a cleanup pass, before a release or milestone, or when the codebase feels heavier than its feature count justifies.

The per-feature workflow. Use when starting any feature, change, or fix: "build F003", "next feature", "add X", "fix Y". Chores build straight through; features run GRILL -> RED -> GREEN -> REVIEW -> MERGE with caps.

The security trigger and review procedure for this project. Use when deciding whether work needs a security pass, and to run one -- "does this need security review?", auth changes, new input surfaces, new tools.

On-demand debt sweep. Use when the owner asks for a cleanup pass, before a release or milestone, or when the codebase feels heavier than its feature count justifies.

The per-feature workflow. Use when starting any feature, change, or fix: "build F003", "next feature", "add X", "fix Y". Chores build straight through; features run GRILL -> RED -> GREEN -> REVIEW -> MERGE with caps.

The security trigger and review procedure for this project. Use when deciding whether work needs a security pass, and to run one -- "does this need security review?", auth changes, new input surfaces, new tools.

On-demand debt sweep. Use when the owner asks for a cleanup pass, before a release or milestone, or when the codebase feels heavier than its feature count justifies.

The per-feature workflow. Use when starting any feature, change, or fix: "build F003", "next feature", "add X", "fix Y". Chores build straight through; features run GRILL -> RED -> GREEN -> REVIEW -> MERGE with caps.

The security trigger and review procedure for this project. Use when deciding whether work needs a security pass, and to run one -- "does this need security review?", auth changes, new input surfaces, new tools.

On-demand debt sweep. Use when the owner asks for a cleanup pass, before a release or milestone, or when the codebase feels heavier than its feature count justifies.

The per-feature workflow. Use when starting any feature, change, or fix: "build F003", "next feature", "add X", "fix Y". Chores build straight through; features run GRILL -> RED -> GREEN -> REVIEW -> MERGE with caps.

The security trigger and review procedure for this project. Use when deciding whether work needs a security pass, and to run one -- "does this need security review?", auth changes, new input surfaces, new tools.

On-demand debt sweep. Use when the owner asks for a cleanup pass, before a release or milestone, or when the codebase feels heavier than its feature count justifies.

The per-feature workflow. Use when starting any feature, change, or fix: "build F003", "next feature", "add X", "fix Y". Chores build straight through; features run GRILL -> RED -> GREEN -> REVIEW -> MERGE with caps.

The security trigger and review procedure for this project. Use when deciding whether work needs a security pass, and to run one -- "does this need security review?", auth changes, new input surfaces, new tools.

On-demand debt sweep. Use when the owner asks for a cleanup pass, before a release or milestone, or when the codebase feels heavier than its feature count justifies.

Bootstrap a new project through a short conversation (at most 5 questions; the agent infers the rest and states its defaults) that ends in an owner-approved one-page PRD, then renders the project deterministically -- AGENTS.md, the iteration/security-review/tech-debt skills, the reviewer and utility subagents with hooks, docs/ (PRD, machine-checked feature list, threat model, gotchas), CI, and the chosen language's toolchain with a green-on-first-run scaffold. Use whenever a project is uninit...

The per-feature workflow. Use when starting any feature, change, or fix: "build F003", "next feature", "add X", "fix Y". Chores build straight through; features run GRILL -> RED -> GREEN -> REVIEW -> MERGE with caps.

The security trigger and review procedure for this project. Use when deciding whether work needs a security pass, and to run one -- "does this need security review?", auth changes, new input surfaces, new tools.

On-demand debt sweep. Use when the owner asks for a cleanup pass, before a release or milestone, or when the codebase feels heavier than its feature count justifies.

Upgrade an EXISTING project bootstrapped from an older ForgeWorks release to the current structure without clobbering hand-filled content. Reconciles the project against a fresh copy of the template: copies missing always-on files, grafts new AGENTS.md rule blocks and subagent sections, applies the language tooling delta, migrates the v4 ledger into features.json state, and reports the rest. Non-destructive and idempotent. Use when a project already has a generated AGENTS.md and the user says...