Menú
SkillsMP ha recopilado 78 skills de douglance/sdlc-plugin. Abre una skill para revisar su origen y sus detalles.
Mostrando 40 de 78 skills recopiladas.
Use for consequential handoffs, blockers, completion reports, requirements, procedures, interface content, or formal documentation that must be easy to act on.
Idioma del texto original: inglés
Use when designing a public API, schema, module boundary, or frontend-backend contract.
Idioma del texto original: inglés
Use when a failure's cause is unknown, evidence conflicts, or an initial fix did not solve the problem.
Idioma del texto original: inglés
Use when tested code must be released with versioning, rollout, smoke checks, and a rollback path.
Idioma del texto original: inglés
Use when a nontrivial change has unsettled interfaces, contracts, file structure, trade-offs, or verification boundaries.
Idioma del texto original: inglés
Use to remove unnecessary generated patterns from the current diff without changing behavior.
Idioma del texto original: inglés
Use when a consequential decision, public contract, or durable rationale must be recorded for future maintainers.
Idioma del texto original: inglés
Use after behavior ships or an interface changes when documentation must be created, corrected, or verified against the source.
Idioma del texto original: inglés
Use when unfamiliar technology or constraints require sourced options and feasibility evidence before choosing an approach.
Idioma del 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 del texto original: inglés
Use when building or restyling a user-facing web interface where art direction and production-quality visual execution matter.
Idioma del texto original: inglés
Use for commits, branching, merge conflicts, versioning, or integration across parallel workstreams.
Idioma del texto original: inglés
Use when requirements are clear and code must be added, changed, or fixed against an observable success criterion.
Idioma del texto original: inglés
Use when implementation should be split into multiple independently verifiable slices or commits.
Idioma del texto original: inglés
Use when the user explicitly wants a plan, design, specification, approach, or decision stress-tested through disciplined questions.
Idioma del 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 del 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 del texto original: inglés
Use to remove dead code, duplication, indirection, or unnecessary complexity while preserving behavior.
Idioma del texto original: inglés
Use when a live service needs observability, incident response, SLOs, runbooks, or continuity work.
Idioma del texto original: inglés
Use when a measured regression, explicit performance target, or profiler evidence identifies work to optimize.
Idioma del texto original: inglés
Use when an accepted specification or plan must become ordered tasks, vertical slices, atomic commits, or parallel work boundaries.
Idioma del texto original: inglés
Use when a validated nontrivial change needs milestones, dependencies, risks, and an explicit out-of-scope boundary.
Idioma del texto original: inglés
Use for independent verification, validation, inspection, and quality judgment beyond whether tests pass.
Idioma del texto original: inglés
Use when a request is ambiguous, high-blast-radius, difficult to reverse, or missing a material product decision.
Idioma del texto original: inglés
Use when a request spans multiple lifecycle phases or the correct next phase is unclear.
Idioma del texto original: inglés
Use for authentication, authorization, secrets, untrusted input, sensitive storage, or an explicit security review.
Idioma del texto original: inglés
Use when a significant change needs a durable specification before implementation can begin safely.
Idioma del texto original: inglés
Use when a behavior change or defect is best defined and protected by a failing test before implementation.
Idioma del texto original: inglés
Use after implementation to probe edge cases, failure modes, malformed input, scale, security, and contradictions.
Idioma del texto original: inglés
Use when creating or reviewing a user-facing layout, state, illustration, document, slide, motion treatment, or rendered visual result.
Idioma del 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 del texto original: inglés
Use when tested code must be released with versioning, rollout, smoke checks, and a rollback path.
Idioma del texto original: inglés
Use when a nontrivial change has unsettled interfaces, contracts, file structure, trade-offs, or verification boundaries.
Idioma del texto original: inglés
Use after behavior ships or an interface changes when documentation must be created, corrected, or verified against the source.
Idioma del texto original: inglés
Use when unfamiliar technology or constraints require sourced options and feasibility evidence before choosing an approach.
Idioma del 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 del texto original: inglés
Use when building or restyling a user-facing web interface where art direction and production-quality visual execution matter.
Idioma del texto original: inglés
Use when requirements are clear and code must be added, changed, or fixed against an observable success criterion.
Idioma del texto original: inglés
Use when the user explicitly wants a plan, design, specification, approach, or decision stress-tested through disciplined questions.
Idioma del 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 del texto original: inglés