ai-workflows

Draft, revise, or refine the workflow idea artifact as the Product Strategist operator before idea-review. Use when shaping an early product opportunity, turning a rough prompt into `./docs/workflows/{slug}/idea.md`, or updating an existing idea artifact with accepted user or review feedback.

Review an idea artifact using two substantive reviewer subagents plus one skeptic before spec creation. Use when the workflow needs review output in ./docs/workflows/{slug}/reviews/idea/round-01.md.

Draft, revise, or update the implementation-ready engineering plan as the Software Architect operator before plan-review. Use when turning an approved spec into `./docs/workflows/{slug}/plan.md`, updating an existing plan, or incorporating accepted plan-review feedback before implementation.

Review `./docs/workflows/{slug}/plan.md` before implementation using two substantive reviewer subagents plus one skeptic. Use when validating implementation readiness, architecture simplicity, restartability, or whether the workflow can advance to `implement-plan`, and write output to `./docs/workflows/{slug}/reviews/plan/round-XX.md`.

Draft, revise, or update the functional product contract as the Product Manager operator before spec-review. Use when turning an approved idea into `./docs/workflows/{slug}/spec.md`, updating an existing spec, or incorporating accepted spec-review feedback before planning.

Review `./docs/workflows/{slug}/spec.md` using two substantive reviewer subagents plus one skeptic before plan creation. Use when validating the functional product contract, observable acceptance, readiness for `plan-create`, or whether the workflow can advance, and write output to `./docs/workflows/{slug}/reviews/spec/round-XX.md`.

Coordinate the full workflow from idea through close-out using the active session as orchestrator, subagents as operators and reviewers, and explicit user gates between major phases. Use when the user wants guided orchestration rather than a one-shot stage run.

Run final fidelity review against implemented behavior, idea/spec/plan alignment, validation and regression gaps, unresolved implementation drift, and docs close-out readiness. Use before workflow closure, and write output to `./docs/workflows/{slug}/reviews/final/round-XX.md`.

Implement or remediate an approved `./docs/workflows/{slug}/plan.md` as the Software Engineer operator using bounded validated code changes, optional execution evidence, and handoff to implementation-review.

Review implemented code, diffs, execution evidence, and validation sufficiency with architecture, security, and QA/product-correctness reviewer lenses. Use when deciding whether implementation can advance to final-review, and write output to `./docs/workflows/{slug}/reviews/implementation/round-XX.md`.

Apply an optional manual pressure-test outside the formal workflow to ideas, specs, plans, implementation summaries or diffs, architecture choices, product decisions, and workflow proposals. This is separate from the mandatory Skeptic reviewer used inside idea/spec/plan review.