douglance

douglance/sdlc-plugin

Skill Claude CodeCodex

Use for consequential handoffs, blockers, completion reports, requirements, procedures, interface content, or formal documentation that must be easy to act on.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use when designing a public API, schema, module boundary, or frontend-backend contract.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use when a failure's cause is unknown, evidence conflicts, or an initial fix did not solve the problem.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use when tested code must be released with versioning, rollout, smoke checks, and a rollback path.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use when a nontrivial change has unsettled interfaces, contracts, file structure, trade-offs, or verification boundaries.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use to remove unnecessary generated patterns from the current diff without changing behavior.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use when a consequential decision, public contract, or durable rationale must be recorded for future maintainers.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use after behavior ships or an interface changes when documentation must be created, corrected, or verified against the source.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use when unfamiliar technology or constraints require sourced options and feasibility evidence before choosing an approach.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use when proliferating rules, exceptions, adapters, or workarounds suggest the underlying model may be wrong and a falsifiable simpler model is needed.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use when building or restyling a user-facing web interface where art direction and production-quality visual execution matter.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use for commits, branching, merge conflicts, versioning, or integration across parallel workstreams.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use when requirements are clear and code must be added, changed, or fixed against an observable success criterion.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use when implementation should be split into multiple independently verifiable slices or commits.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use when the user wants a proposal stress-tested against the domain model while terminology and project decision records are updated.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use when the user explicitly wants a plan, design, specification, approach, or decision stress-tested through disciplined questions.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use to create or review a formal, traceable lifecycle artifact or phase handoff that another person or system must consume.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use to remove dead code, duplication, indirection, or unnecessary complexity while preserving behavior.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use when a live service needs observability, incident response, SLOs, runbooks, or continuity work.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use when a measured regression, explicit performance target, or profiler evidence identifies work to optimize.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use when an accepted specification or plan must become ordered tasks, vertical slices, atomic commits, or parallel work boundaries.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use when a validated nontrivial change needs milestones, dependencies, risks, and an explicit out-of-scope boundary.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use for independent verification, validation, inspection, and quality judgment beyond whether tests pass.

douglance/sdlc-plugin

Skill Claude CodeCodex

Use when a request is ambiguous, high-blast-radius, difficult to reverse, or missing a material product decision.