Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →florianbruniaux/plan-pipeline-eng-review
Engineering architecture gate: lock architecture, diagrams, edge cases, and test matrix before writing implementation code
Passed 13 of 23 test cases with the skill, and 7 of 23 without it.
and 8 more in the full report
8 fixed5 passed either way8 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our product scope for the automated recurring invoice collection feature was just approved by leadership. Before our team writes any code, I need a detailed engineering spec to guide implementation. Please take these product requirements and map out the technical architecture. Generate Mermaid diagrams for the component relationships, the primary sequence flow, and domain state transitions. Also analyze sync vs async boundaries, systematically list edge cases and failure modes with recovery paths, audit security trust boundaries for external input payloads, and provide a test coverage matrix across unit, integration, and E2E layers along with key architectural blockers.
| Checked | Without skill | With skill |
|---|---|---|
| Restates the feature scope in 1 to 2 sentences. | Passed | Passed |
| Includes a failure mode inventory with recovery paths. | Passed | Passed |
| Refrains from writing executable implementation code. | Missed | Passed |
The instructions your model reads when the skill loads.
Post-direction, pre-implementation command. Takes validated product direction and returns a buildable technical spec with diagrams. Forces the system to think through architecture before a single line of implementation code is written.
Use after /plan-pipeline:ceo-review has locked direction. Still in plan mode.
Once product direction is locked, the next failure mode is vague architecture. "The system will handle it" is not a plan. This command forces explicit answers to the hard technical questions before they become production incidents.
The key unlock: forcing diagram generation. Diagrams surface hidden assumptions that prose keeps vague. A sequence diagram makes you specify who calls what. A state machine makes you enumerate every failure mode explicitly.
/plan-pipeline:ceo-review or equivalent)| Output | Why it matters |
|---|---|
| Architecture diagram (Mermaid) | Makes component boundaries explicit |
| Data flow diagram | Shows where data transforms and who owns what |
| State machine for core flow | Forces enumeration of all states including failures |
| Sync vs async boundary decisions | Prevents "just make it async" without reasoning |
| Failure mode inventory | Every failure path, not just happy path |
| Trust boundary map | Where do you accept external input? What do you validate? |
| Test matrix | What needs to be tested and at which layer |
test cases passed, vs 7 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.