pi-execflow

Sequentially drain ready br issues or tk tickets through the existing ship chains with retry limits and progress state.

Update a work item with a concise execution note and close it only when validation and review evidence prove the acceptance criteria. Use for prompts that finalize work-item status after manual execution chains.

Review work items, ExecPlan delivery, or arbitrary code changes with evidence-backed findings. Reviews are read-only by default and create tracker follow-ups only when explicitly requested with --create-followups.

Implement or fix a work item using minimal diffs while preserving scope, local conventions, and testability. Use for prompts that change code or apply validation/review fixes.

Validate work-item changes using concrete evidence, exact commands, and explicit gap reporting. Use for validation prompts and review passes that audit proof.

Create a self-contained ExecPlan from a brainstorm artifact and/or a user brief. Follows the project's .execflow/PLANS.md spec. Applies the Ousterhout design lens. Use when creating execution plans, turning ideas into implementable steps, or wants a PRD/RFC/brainstorm turned into a step-by-step plan.

Convert an ExecPlan's milestones into tracked work items, automatically selecting tk tickets or br issues from repo context unless the user forces a tracker with --tk or --br. Use when the user wants one entrypoint that works across both tracker backends.

Interactive design brainstorming for a topic or feature idea. Explores project context before implementation, asks one focused question at a time, compares 2-3 approaches, obtains user approval, writes a reviewed brainstorm/design artifact under .execflow/plans/, and gates transition to ExecPlan creation.

Stress-test an existing ExecPlan through a relentless, interactive grilling session. Challenges plan assumptions against the codebase, sharpens terms, resolves decision branches one at a time, and updates the ExecPlan as decisions crystallize.

Build an implementation-ready work-item spec by combining resolution, scope control, and validation framing. Use for prompts that normalize a work item into explicit acceptance criteria, constraints, non-goals, and required proof.

Resolve work items reliably from .tickets/ or .beads/ and connect them to ExecPlans when available. Use before manual implementation, planning, validation, or review.