Claude Skills by dikamilo

Archive a completed change or effort — move its folder to context/archive/ and stamp it archived.

Think through a raw idea before committing to it — weigh alternatives, price doing nothing, and route to a change, an effort, or nothing at all.

Feedback-loop-first diagnosis for bugs and performance regressions. Use when the user says something is broken/slow/throwing/failing/crashing/hanging/flaky/regressed, reports wrong output, asks to debug, diagnose, or find the root cause of a defect or perf problem.

Mine a brownfield codebase for its domain vocabulary and seed the project glossary.

Actively sharpen the ubiquitous language in foundation/glossary.md. Fire the instant a domain term clashes with an existing definition, is vague or overloaded (an "account" that might be a Customer or a User), or finally gets pinned down — mid-task, not only when asked. Capture or correct the term, then hand back to the interrupted work.

Interview to settle the problem framing and alternatives for a change or effort before planning — writes frame.md.

Review a finished change against its plan — drift, safety, patterns, standards compliance — and report.

Execute the next pending phase of a change's plan, verify it, and commit.

Scaffold the dx- SDLC state tree (context/) in this project and seed the baseline standards.

Record one finding — a warning or a decision-with-rationale — as an append-only entry in foundation/lessons.md.

Start a new piece of work — creates a change or an effort and points you at the next step.

Review a change's plan before implementation — substance, feasibility, fit, and standards match.

Interview and write plan.md for a change — matches standards, surfaces priors, owns Progress.

Hunt the codebase for refactor opportunities, present them inline, and promote the ones you pick into changes.

Loads a dx shared reference document by topic. Invoked by other dx- skills to pull in shared reference material (change-md, effort-md, progress-format, plan-template, plan-data-model, plan-api-contracts, plan-failure-modes, interview, module-design, design-lenses, knowledge-layer, review-report, untrusted-content).

Investigate one topic — codebase or external doc — and write it down with provenance for a plan to lean on.

Triage findings from a plan-review or impl-review report and apply the fixes you choose.

Decompose an effort into an ordered list of vertical slices and write roadmap.md.

Mine the project's real conventions from tooling, code, and docs and write them into the standards layer.

Create, edit, or promote a standard in context/standards/ — from the conversation, a graduated lesson, or another project.

Execute the next pending phase of a change's plan test-first — red, green, refactor — and commit.