peak-workflow

Plugin peak-workflow from marketplace peakflames-plugins in peakflames/claude-plugins-peakflames. Commands read from the repo's manifest — 2 days ago.

Skills (15)

• add

  Adds new epic(s) to the implementation plan from a natural language description. Epics reference TOR requirement IDs from docs/requirements/*.feature.md as their Requirements Anchors — the TOR ID is the acceptance criterion and the Given/When/Then is the verification. Use when the user wants to add

• capture-requirements

  Derives formal Gherkin-style TOR requirements (.feature.md files) from product-vision.md and concept-of-operations.md. Main agent adopts a seasoned-PM persona to author feature files autonomously; Haiku sub-agent verifies traceability and writes .feature.tracing.json sidecars. Changes to merged requ

• discover

  Adaptive discovery interview that produces product-vision.md and concept-of-operations.md. Use when starting a new project (greenfield) or evolving an existing project's direction (brownfield). Creates a docs/{task-short-name} branch if on develop/main/master so all planning artifacts travel through

• mockup

  Low-fidelity UX prototyping on the docs/ branch. Turns ConOps operational scenarios into a screen inventory, per-scenario screen flows, and grayscale HTML wireframes, then feeds the screen and control names back into the ConOps steps so /peak-workflow:capture-requirements derives TORs against named

• new-project

  Front-door router for newcomers. Reads the project's format stamp to tell a fresh project, an existing peak-workflow project, and one that needs /peak-workflow:upgrade apart, and dispatches to the correct entry point. Writes no state files. Use when starting work on a project for the first time and

• pause

  Pauses current epic implementation and saves progress to a handoff file. Use when stopping mid-epic before the session ends. Triggers on: "pause epic", "stop epic", "save progress", "I need to stop for today", "save my progress", "I'm done for now", "let's pick this up later". Note: If the user says

• plan-project

  Derives implementation plan (phases, epics, specs) from the TOR requirements baseline (docs/requirements/*.feature.md). Must be run after /peak-workflow:capture-requirements. Operates on the same docs/{task-short-name} branch as discover and capture-requirements. Use after the requirements baseline

• quick-fix

  Lightweight path for trivial items — bugs, copy changes, small enhancements (~2 hours or less). Creates a `hotfix/` branch, plans and implements the fix with applicable quality gates (plus an owner-approved amendment path for one wrong requirement), and ships via prompted solo mode (local merge) or

• refresh-docs

  Refreshes architecture.md and design-notes.md to match the as-built codebase by reading source files and session handoffs. Use after completing a phase or before a release. Triggers on: "refresh docs", "update architecture", "sync documentation", "docs are stale", "docs are out of date", "architectu

• setup

  Audits CLAUDE.md for required sections and stubs architecture.md and design-notes.md. Use for first-time project setup before starting epics. Triggers on: "setup project", "audit CLAUDE.md", "project setup", "prepare project for epics", "initialize project", "first time setup", "configure CLAUDE.md"

• start-epic

  Implements an epic — loads spec, loads TOR requirements from feature files, plans with TOR-driven user story tasks, implements, and verifies each TOR's Given/When/Then. Use when the user wants to begin or resume working on a specific epic. Triggers on: "start epic", "implement epic", "begin epic", "

• status

  Displays a project status dashboard — epic progress, requirements coverage and health, active work, stale paused epics, and next actions. Strictly read-only — does not modify any files. Triggers on: "status", "project status", "what's the progress", "how far along are we", "show me the dashboard", "

• triage

  Advisory routing for an incoming GitHub issue or ad-hoc request — sizes the request against the TOR requirements baseline, product vision, and ConOps, then recommends one of HEAVY / AMEND / EPIC / TRIVIAL. On user confirm, dispatches `/add`, `/quick-fix`, or (for a change to one existing requirement

• upgrade

  Brings a project's peak-workflow files forward to the format this plugin version reads, one numbered step at a time. Reads the format stamp (docs/.peak-workflow.toml; missing = format 0), runs each pending step's detect check, previews and applies it on a docs/upgrade-format-N branch with one commit

• wrapup-epic

  Independent verification review of a completed epic — verifies each TOR requirement's Given/When/Then, closes out, and orients to next steps. Use after an epic is implemented and needs independent review. Triggers on: "wrapup epic", "verify epic", "review epic", "close epic", "is epic N done?", "che

Slash commands (1)

• /peak-workflow:newtask