sdlc-skills

Use after the spec is clear and before implementation, when a coding task involves real architecture or design trade-offs - data model, API shape, build-vs-buy, a new module, choosing a library, or how the agent's context and guardrails are set up. Make sure to use this whenever you ask "how should we structure this", "what's the architecture", "which library", or faces any non-trivial structural decision, even if he doesn't say "design". Second step of the SDLC loop; skip it for trivial changes.

Use during active implementation of a planned, tested feature - once a spec and failing tests exist and it's time to write code. Drives the agent to implement against the spec + tests, reserves your attention for the hard 20% (ambiguity, edge cases, correctness), and reviews code as it appears instead of accepting it blind. Make sure to use this whenever you are coding a feature that already has a spec/tests, or says "now build it", "make the tests pass", "implement the slice". Fourth step of the SDLC loop.

Use on a weekly cadence, or after a rough project, to turn logged failures into durable improvements. Reads the agent-run log, clusters recurring agent failures, encodes each into an AGENTS.md rule or checklist, and updates the KPI tracker so the trend is visible. This is the compounding self-improvement step that makes you measurably better at directing agents over time. Make sure to use this whenever you say "weekly review", "retro", "what did we learn", "update my rules", or "let's improve the loop". Final step of the SDLC loop - it feeds the next cycle.

Use at the START of any coding task, feature, or project - before design or code. Turns a rough idea or request into a clear, testable spec that clarifies real intent, surfaces edge cases, and deliberately hunts for the simplest path to the same outcome (fewest steps, least complexity). Make sure to use this whenever you say "let's build", "I want to add", "new feature/project", "plan this out", or hands over a vague coding request - even if he doesn't say the word "plan". First step of the SDLC loop.

Grade agent output before it ships, and log it. Use when agent-produced code is about to ship - a PR, a merge, a deploy, or "is this ready". Runs deterministic gates first, then grades the change against a short rubric (spec adherence, error handling, approach, reviewability), and logs the run so the self-improvement loop has data. This is the ONLY place an LLM judge is allowed, and only for code review. Make sure to use this whenever you say "review this", "before I ship/merge", "is this ready", or hands over a diff/PR. Fifth step of the SDLC loop.

Use BEFORE generating implementation code for any feature with verifiable behavior. Writes the tests (and evals, if output quality is judgment-based) FIRST, as the contract that defines "correct," so the agent implements against a real target instead of a vibe check. Make sure to use this whenever you say "implement", "write the code for", "build the function/endpoint/feature" - intercept and do tests first - and also on "write tests" or "add coverage". Third step of the SDLC loop and the single highest-leverage habit.