workflowlisted

# workflow — Project Workflow Explicitly called by user to start or continue the product development workflow. Never auto-triggered. Supports running the full pipeline or jumping to any stage. ## Doc Paths All paths are relative to `workspace/` (the Claude Code working directory). | Doc type | Path | | -------------- | ------------------------------------------------------ | | Product | `docs/product/` | | Backend Engr. | `docs/engineering/` (common/, service/, worker/, web/) | | Frontend Engr. | `docs/engineering/frontend/<entity>.md` | | Schema | `docs/engineering/common/schemas/<entity>.md` | | API spec | `docs/engineering/service/api/<entity>.md` | | Workflows | `docs/engineering/worker/workflows/<entity>.md` | | Spec & Plan | `docs/superpowers/` | | Archived | `docs/superpowers/archived/` | ## Hard Rules - **Git worktrees** — invoke `superpowers:using-git-worktrees` at the start of every stage that produces file output. Never work directly in the main worktree. - **Approval gates** — pause and wait for explicit user approval before advancing to the next stage. Never chain stages automatically. - **Model enforcement** — spawn a subagent with the specified model. Never run a stage on the wrong model. - **Halt on missing prerequi