SWE Plan Governance

0•

Applies an opinionated software engineering rubric to build plans, architecture specs, and PRDs to enforce minimal scope, blast radius control, and verifiable proof.

The SWE Plan Governance skill acts as an architectural gate and review rubric for technical specifications, RFCs, PRDs, and v1.x implementation plans before any code is written. By evaluating proposals across four core pillars—Minimal scope, Diagnosable failure paths, Blast radius accounting, and Verifiable proof of completion—along with Pillar 0 system reconnaissance, it prevents premature abstractions, hidden one-way doors, and unverified assumptions. Whether used in author mode to scaffold disciplined project docs or review mode to audit proposed architectures, this skill ensures production-ready engineering standards from day one.

主な機能

01Blast radius pricing that explicitly identifies undo classes, shields, and tripwires for high-risk decisions
02Scope gating using the Ponytail minimal principle to eliminate premature abstractions and speculative features
03Diagnosability enforcement to bake in observability, reproduction strategies, and loop-stop conditions up front
04Verifiable proof standards that require measurable done-criteria, actual test execution, and closed-loop data flows
05Pillar 0 Reconnaissance verification to ensure plans are grounded in actual codebase traces rather than assumptions
060 GitHub stars

ユースケース

01Establishing enforceable coding and architectural contracts within project AGENTS.md and CLAUDE.md files
02Auditing PRDs, RFCs, and implementation specs to catch architectural liabilities before engineering work begins
03Authoring v1.x build roadmaps and technical plans that adhere to strict engineering governance standards