This skill should be used when a project needs the lifecycle framework adapted to its specific product type (MVP, startup, data platform, enterprise, or regulated product), team size, or risk profile. Triggers when the user asks "what phases are mandatory for us", "can we skip Gate B", "we're building an MVP — what's the minimum governance", or when Phase 1 is starting and the governance configuration must be decided.
From agile-lifecyclenpx claudepluginhub nsalvacao/nsalvacao-claude-code-plugins --plugin agile-lifecycleThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Generates FastAPI project templates with async routes, dependency injection, Pydantic schemas, repository patterns, middleware, and config for PostgreSQL/MongoDB backends.
The framework is designed to be adapted, not applied uniformly. A startup validating an MVP needs different governance intensity than an enterprise platform migration. Lifecycle tailoring is a Phase 1–2 decision that determines which phases to compress, which gates are mandatory, which artefacts to simplify, and which quality thresholds to apply. Done correctly, tailoring prevents over-engineering of governance for simple products and under-engineering of controls for complex or regulated ones.
Assess the product and delivery context against four primary tailoring dimensions:
Load references/lifecycle-overview.md for the standard phase map and default gate criteria.
Match the context to one of the standard profiles (or define a hybrid):
MVP/Startup profile: Compress Phases 1–2 into a single framing week. Gate A and B are informal checkpoints. Phase 3 runs in parallel with early Phase 4 sprints. Gate C is a team self-assessment. Mandatory artefacts reduced to: phase contract, risk register, backlog.
Data platform profile: Full Phase 1–2 required. Gate A mandatory (data governance sign-off). Phase 3 must include data model artefacts. Gate C includes data quality and lineage evidence. Phase 5 (Hardening) has extended test windows.
Enterprise integration profile: All phases and gates mandatory. Phase 2 must produce integration architecture. Gate B requires architecture review board sign-off. Phase 4 has a mandatory security sprint. Gate E requires operational readiness review.
Regulated product profile: All phases, all gates, all artefacts mandatory. Additional compliance artefacts required (audit log, traceability matrix, validation protocol). Gate reviews require external or independent reviewer sign-off.
For the selected profile, document which phases can be compressed or skipped:
For each gate (A–F), classify as:
Record gate classification in the lifecycle tailoring decision document. Reference docs/phase-essentials/ for gate defaults per phase.
For each artefact in references/artefact-catalog.md, classify as:
Document simplification decisions with rationale.
Create a lifecycle tailoring decision document as a Phase 1 artefact:
Add this document to the Phase 1 evidence index. It will be referenced at all subsequent gate reviews as the authority for governance configuration.
At each gate review, validate that the tailoring decisions are still appropriate:
references/lifecycle-overview.md — Standard phase map, default gate criteria, phase dependenciesreferences/artefact-catalog.md — Full artefact list with phase assignment and mandatory/optional classificationdocs/phase-essentials/ — Per-phase essentials cards with tailoring guidance