eng

Orchestrator for the eng pipeline. Runs the five skills in order — scope → grill → eng-review → tdd → execute — driven entirely off the phase recorded in the .plan doc, pausing at a gate between each so the user stays in control. Picks up wherever the doc left off, so it's also "resume my planning flow". Use when the user wants to run the whole plan-to-ship pipeline rather than invoking skills one at a time. Triggers: "eng flow", "run the pipeline", "plan to ship", "take this from idea to code", "resume the flow".

Third pass of the eng pipeline. An engineering-manager review of a .plan doc: rates the plan across architecture, edge cases, test coverage, performance, and — critically — consistency with how THIS codebase already builds things (APIs, components, patterns), so the eventual code matches house style. Scores each dimension 0-10, explains what would make each a 10, and folds the fixes back into the doc. Use when a grilled .plan doc is ready for architectural review before defining tests. Triggers: "eng review", "review the plan", "review the architecture", "lock in the plan".

Final pass of the eng pipeline. Implements a fully-planned .plan ticket: writes the unit tests the doc specified (TDD — failing first), implements against the acceptance criteria following the repo's conventions, runs the tests until they pass, then verifies the acceptance criteria and walks the manual QA checklist. Updates the doc's Work Log and the README status. Use when a tested .plan doc is ready to build. Triggers: "execute", "implement this", "build this ticket", "do the work".

Second pass of the eng pipeline. Reads the Open Questions a scope doc already recorded, grills the user about them one batch at a time, then adds its own engineering and business questions to close remaining ambiguity — exploring the codebase a little more if it needs context. Writes answers into the doc's Decisions section and sharpens scope/acceptance criteria. Use when a .plan doc exists and needs its requirements nailed down. Triggers: "grill me", "ask me questions about this", "tighten the requirements", "resolve open questions".

Front door of the eng pipeline. Takes a task description, explores the codebase deeply, decides (with the user) whether it needs a Jira ticket and whether to split into one or many tickets, then writes a planning doc per ticket into the project's .plan folder — including real file:line touchpoints, house conventions, and open questions for the next step. Use when the user describes a feature/task and wants it scoped, broken down, or turned into Jira tickets. Triggers: "scope this", "break this down", "turn this into tickets", "plan this feature".