Overview
The five end-to-end workflows the plugins ship — feature implementation, UI verification, debugging, business analysis and project context — who runs each step, where people decide, and which plugins each one needs.
Feature implementation
How a feature, ticket or plan goes from request to verified change — a committed plan, implementer subagents working from it, a verification pyramid and a final phase where code review and functional verification run in parallel.
UI verification
How implemented UI is judged against its Figma design — fresh Playwright-CLI capture, a read-only design judge, a verdict of PASS, FAIL or VERIFICATION NOT RUN, and a per-item verify-fix loop with an iteration budget and an escalation gate.
Debugging
How a bug is fixed at its root cause — symptom, reproduction, a failing test, a causal chain with evidence, the reach of the fix, a minimal change and a regression guard — and when the work leaves for a plan instead.
Business analysis
How discovery workshop material becomes Jira-ready epics and stories and a delivery roadmap — five human review gates recorded in a ledger, read-only worker subagents, a hook that blocks Jira writes before Gate 2, and Explore and import entry points.
Project context
How a repository's own Claude Code context is set up and kept true, and how a project's shared knowledge base — the `<slug>-context` repository — is created, connected to code repositories, read with citations and written through reviewed branches.