How a feature travels from request to production: which skill enters at each stage, which agent does the work, on which model, and in which ponytail mode. Click a skill to see where it shows up in the flow.
Opens workstreams, sets order and the schema queue, watches machine load and context size, merges PRs, talks to the owner. Writes no code, not even through subagents.
Owns one feature end to end: spec, plan, subagents, reviews, PR. Answers the owner directly on checkpoints and mockups, and reports cross-workstream decisions to the orchestrator in one line.
Do one task each (implementer, reviewers, planner, explorer) and never spawn other agents. They get their mode and skills from the briefing.
Grouped by source plugin. Everything here is a public plugin or skill; this stack only decides where each one enters.
frontend-design and taste open up directions in mockups; implementation loads only impeccable, which holds the finish in production code.
The impeccable detector cleans a mockup before the owner sees it; impeccable-finish-reviewer compares the shipped screen, from real screenshots, against the approved mockup.
test-driven-development makes the test fail first; verification-before-completion only allows "done" with the command run and its output in hand.
systematic-debugging works one failure methodically; dispatching-parallel-agents opens one agent per unrelated failure, and checks that parallel tasks touch no shared files.
security-audit enters early on sensitive specs and before the PR; claude-security (optional) deep-scans finished code before release.
The planner uses writing-plans in ponytail ultra to cut what the spec does not ask for, so each implementer gets a task already the right size.
Tokens. When a wave of tasks closes above this, the workstream writes its handoff note and the orchestrator clears its context, then sends a short briefing back.
Auto-compact safety net (autoCompactWindow), for when nobody checked in time.
Tasks at once per workstream, because every workstream shares one machine.
Where each workstream keeps its handoff note, on its own branch, with a fixed template and a clean-session checklist.
Auto-archive on PR close. Archiving a session kills its background agents; keep it off while sessions open spec PRs and keep working.
Lines of code leaving the main session. It only orchestrates, merges and talks.