lights-out-swe-plugin
lights-out-swe-plugin contient 13 skills collectées depuis RCSnyder, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
Analyze phase. Turns scope.md and design.md into readiness.md with traceability, truths, build order, and scope-risk checks before BUILD.
Audit preferences.md stack choices against input docs for orthodox, idiomatic fit. Use before /expand when you want to validate that your technology choices match the problem domain.
Execute BUILD, ITERATE, or verify-fix work in small, test-first vertical slices. Use for multi-file implementation, failing tests, root-cause debugging, scope-creep risk, or when maintainability matters.
Build phase. Takes scope.md, design.md, and readiness.md and writes the actual code, tests, and deployment config in vertical slices.
Deploy phase. Push to the deployment target, verify it's live, write README and DELIVERY.md.
Design phase. Takes scope.md and produces design.md with architecture, directory structure, interfaces, integration details, and justified complexity exceptions.
Distill raw input materials into structured reference docs. Use when docs/input/ contains messy client briefs, API specs, meeting notes, or domain knowledge that needs structuring before EXPAND.
Start a new project. Expands a one-liner into scope.md with problem, smallest useful version, stable acceptance criteria IDs, stack, deployment target, and data model.
Scaffold the Lights Out SWE harness (copilot-instructions.md, preferences.md, LIGHTS-OUT-SWE.md, scaffolding/, docs/input/, .gitignore) into the current repo. Run once to set up a new repository before starting the pipeline.
Iterate on a shipped project. Reads feedback, deferred items, and the existing codebase to propose and build the next version. Use after delivery when the client wants changes, new features, or when you're refining product-market fit.
Reconcile scaffolding documents against the codebase. Detects and fixes drift between scope.md, design.md, readiness.md, log.md, and the actual code.
Review phase. Audit built code for correctness, readability, architecture, security, and performance before reconcile and verify.
Verify phase. Run all tests, verify acceptance criteria, check security, confirm deployment readiness.