Use to remove dead code, duplication, indirection, or unnecessary complexity while preserving behavior.
Idioma do texto original: inglês
Menu
Skills neste repositório
O SkillsMP coletou 78 skills de douglance/sdlc-plugin. Abra uma skill para revisar a origem e os detalhes.
douglance/sdlc-pluginMostrando 38 de 78 skills coletadas.
Use to remove dead code, duplication, indirection, or unnecessary complexity while preserving behavior.
Idioma do texto original: inglês
Use when a live service needs observability, incident response, SLOs, runbooks, or continuity work.
Idioma do texto original: inglês
Use when a validated nontrivial change needs milestones, dependencies, risks, and an explicit out-of-scope boundary.
Idioma do texto original: inglês
Use for independent verification, validation, inspection, and quality judgment beyond whether tests pass.
Idioma do texto original: inglês
Use when a request is ambiguous, high-blast-radius, difficult to reverse, or missing a material product decision.
Idioma do texto original: inglês
Use after implementation to probe edge cases, failure modes, malformed input, scale, security, and contradictions.
Idioma do texto original: inglês
Use when creating or reviewing a user-facing layout, state, illustration, document, slide, motion treatment, or rendered visual result.
Idioma do texto original: inglês
Use for consequential handoffs, blockers, completion reports, requirements, procedures, interface content, or formal documentation that must be easy to act on.
Idioma do texto original: inglês
Use for consequential handoffs, blockers, completion reports, requirements, procedures, interface content, or formal documentation that must be easy to act on.
Idioma do texto original: inglês
Use when designing a public API, schema, module boundary, or frontend-backend contract.
Idioma do texto original: inglês
Use when a failure's cause is unknown, evidence conflicts, or an initial fix did not solve the problem.
Idioma do texto original: inglês
Use when tested code must be released with versioning, rollout, smoke checks, and a rollback path.
Idioma do texto original: inglês
Use when a nontrivial change has unsettled interfaces, contracts, file structure, trade-offs, or verification boundaries.
Idioma do texto original: inglês
Use to remove unnecessary generated patterns from the current diff without changing behavior.
Idioma do texto original: inglês
Use when a consequential decision, public contract, or durable rationale must be recorded for future maintainers.
Idioma do texto original: inglês
Use after behavior ships or an interface changes when documentation must be created, corrected, or verified against the source.
Idioma do texto original: inglês
Use when unfamiliar technology or constraints require sourced options and feasibility evidence before choosing an approach.
Idioma do texto original: inglês
Use when proliferating rules, exceptions, adapters, or workarounds suggest the underlying model may be wrong and a falsifiable simpler model is needed.
Idioma do texto original: inglês
Use when building or restyling a user-facing web interface where art direction and production-quality visual execution matter.
Idioma do texto original: inglês
Use for commits, branching, merge conflicts, versioning, or integration across parallel workstreams.
Idioma do texto original: inglês
Use when requirements are clear and code must be added, changed, or fixed against an observable success criterion.
Idioma do texto original: inglês
Use when implementation should be split into multiple independently verifiable slices or commits.
Idioma do texto original: inglês
Use when the user explicitly wants a plan, design, specification, approach, or decision stress-tested through disciplined questions.
Idioma do texto original: inglês
Use when the user wants a proposal stress-tested against the domain model while terminology and project decision records are updated.
Idioma do texto original: inglês
Use to create or review a formal, traceable lifecycle artifact or phase handoff that another person or system must consume.
Idioma do texto original: inglês
Use to remove dead code, duplication, indirection, or unnecessary complexity while preserving behavior.
Idioma do texto original: inglês
Use when a live service needs observability, incident response, SLOs, runbooks, or continuity work.
Idioma do texto original: inglês
Use when a measured regression, explicit performance target, or profiler evidence identifies work to optimize.
Idioma do texto original: inglês
Use when an accepted specification or plan must become ordered tasks, vertical slices, atomic commits, or parallel work boundaries.
Idioma do texto original: inglês
Use when a validated nontrivial change needs milestones, dependencies, risks, and an explicit out-of-scope boundary.
Idioma do texto original: inglês
Use for independent verification, validation, inspection, and quality judgment beyond whether tests pass.
Idioma do texto original: inglês
Use when a request is ambiguous, high-blast-radius, difficult to reverse, or missing a material product decision.
Idioma do texto original: inglês
Use when a request spans multiple lifecycle phases or the correct next phase is unclear.
Idioma do texto original: inglês
Use for authentication, authorization, secrets, untrusted input, sensitive storage, or an explicit security review.
Idioma do texto original: inglês
Use when a significant change needs a durable specification before implementation can begin safely.
Idioma do texto original: inglês
Use when a behavior change or defect is best defined and protected by a failing test before implementation.
Idioma do texto original: inglês
Use after implementation to probe edge cases, failure modes, malformed input, scale, security, and contradictions.
Idioma do texto original: inglês
Use when creating or reviewing a user-facing layout, state, illustration, document, slide, motion treatment, or rendered visual result.
Idioma do texto original: inglês