playbook

Plugin playbook from marketplace claude-code-playbook in femitfash/claude-code-playbook. Commands read from the repo's manifest — 6 days ago.

Skills (9)

• debug

  Use when a test is failing, a production issue occurs, or unexpected behavior needs systematic root cause analysis. Reproduces the failure, builds a hypothesis tree, tests one hypothesis at a time with evidence, and never edits files. Hands off to the implementer skill once root cause is confirmed.

• grill-me

  Use proactively, before any planning or coding, when the user starts a new project or a non-trivial feature whose requirements are not already settled in a PRD.md or DESIGN.md. Also use when the user says "grill me", wants to stress-test a plan, or has an unresolved design ambiguity. Interviews the

• implementer

  Use right after the user approves a plan (for example when plan mode is exited with approval), or when asked to build from an approved plan file in .claude/plans/. Executes it test-first, in small commits, scope-locked to the plan, then hands off to phase-gate. Do not use when there is no approved p

• phase-gate

  Use when an implementation of an approved plan is finished, before reporting it done, and before opening a PR or closing a phase milestone. Runs the review gate (the bundled /code-review and /security-review when they can be run, otherwise a direct review of the diff, plus project-specific checks) a

• planner

  Use when starting any non-trivial implementation work — new packages, subsystems, schema changes, protocol changes, phase transitions, or multi-file changes. Produces a concrete, phase-scoped plan and refuses to code until the user approves.

• project-init

  Use to bootstrap a new project from an existing DESIGN.md. Runs a 5-step, approval-gated initiation: project CLAUDE.md, rules, Phase 0 plan, execution with review gate, and closeout.

• quick-fix

  Use whenever the user asks to fix a bug, make a small change, or add a small feature in an existing codebase and the goal is clear. Reproduces first, writes a failing regression test before changing code, makes the smallest fix, and runs the tests before reporting. Use this instead of editing straig

• resume

  Use at the start of a session to pick up mid-project work. Orients on the design doc, git state and test status, then confirms direction before any code is written.

• security-grill-me

  Use before planning any feature that handles authentication, authorization, user data, multi-tenancy, secrets, financial transactions, or external integrations. Interrogates the security design one question at a time until every threat vector is modeled and every trust boundary is explicit — before

Hooks (2)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh"

• Stop

  "${CLAUDE_PLUGIN_ROOT}/hooks/verify-on-stop.sh"