sergdort

Interview the user relentlessly about a technical design or architecture until every major decision is examined, justified, and stress-tested. Use when the user wants to pressure-test a system design, validate an architecture, compare options, or mentions…

Run focused read-only GitHub repository research with the optional custom github_librarian agent. Use only when the user invokes $github-librarian.

Start the explicit Architect workflow for non-trivial feature work, refactors, and architecture decisions. Use only when the user invokes $architect.

Decompose the active Architect workflow's plan.md into a runnable tracer and dependency-ordered vertical tickets. Use only when the user invokes $decompose.

Create or update the explicit Architect workflow's reviewed implementation plan in plan.md. Use only when the user invokes $plan-feature.

Run the active Architect workflow's approved ticket queue serially through custom developer dispatch, review, human checkpoints, and local commits. Use only when the user invokes $start-work.

Use whenever writing, changing, or reviewing tests for app logic built with the CombineFeedback Swift library. For designing or refactoring the machines themselves, use the combinefeedback-state-machines skill instead.

Use whenever building, changing, or reviewing app logic that uses the CombineFeedback Swift library.

Interview the user relentlessly about a technical design or architecture until every major decision is examined, justified, and stress-tested. Use when the user wants to pressure-test a system design, validate an architecture, compare options, or mentions…

Interview the user relentlessly about a product idea, feature, or strategy until every assumption is surfaced and stress-tested. Use when user wants to pressure-test a product concept, validate their thinking, or mentions "grill me" in a product context.