From waterfall-lifecycle
This skill should be used when creating, completing, or reviewing a waterfall lifecycle artefact. Ensures artefacts follow templates, satisfy completeness requirements, and are ready for gate evidence submission with correct closure obligations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/waterfall-lifecycle:artefact-authoringThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Every waterfall phase produces artefacts that serve as evidence at gate reviews. This skill ensures artefacts are authored against their designated templates, meet the evidence threshold required for their gate, and are registered in the evidence index. It also tracks closure obligations — the mandatory actions required for each artefact at phase end.
Every waterfall phase produces artefacts that serve as evidence at gate reviews. This skill ensures artefacts are authored against their designated templates, meet the evidence threshold required for their gate, and are registered in the evidence index. It also tracks closure obligations — the mandatory actions required for each artefact at phase end.
exists to approved)Identify the artefact by its ID or name in skills/artefact-authoring/references/artefact-catalog.md:
template path — this is the authoritative structuregate this artefact must satisfyevidence_threshold required for that gate (exists / reviewed / approved)closure_obligation — what must happen to this artefact at phase endOpen the template at the path identified in Step 1. Use the {{placeholder}} sections as a mandatory guide:
Complete every mandatory section:
Determine what must happen to this artefact at phase end based on its closure_obligation:
baselined — artefact must be version-locked and tagged; no further edits without change controlarchived — artefact moves to the phase archive and is no longer actively maintainedhanded_over — artefact must be formally transferred to the receiving team or stakeholderupdated — artefact requires a specific update at phase closure (e.g., final status summary)closed — artefact requires a formal closure action (e.g., all items resolved, closure statement signed)Plan for this obligation before phase closure — do not discover it at gate review time.
Confirm the artefact meets its required gate evidence threshold:
exists — file is present, named correctly, and registered in the evidence indexreviewed — artefact has been reviewed by the designated reviewer role; review record existsapproved — artefact has formal sign-off from the designated approver; approval record exists and is referencedIf the artefact is authored to exists level but the gate requires approved, this is a gap — escalate or plan the review/approval process before gate date.
If a JSON or YAML schema exists for this artefact type (check schemas/):
Add the artefact to the evidence index at .waterfall-lifecycle/evidence/:
exists to reviewed or approvedexists when the gate requires approved is a structural gap that will block the review.skills/artefact-authoring/references/artefact-catalog.md — Abbreviated catalog with phase 1 artefacts and transversal objectsreferences/artefact-catalog.md — Full artefact catalog for all phasesreferences/lifecycle-overview.md — Phase-to-gate mapping and artefact contextschemas/ — JSON/YAML schemas for structured artefact typesnpx claudepluginhub nsalvacao/nsalvacao-claude-code-plugins --plugin waterfall-lifecycleValidates phase gates (LOM, ABM, IOC, PRM) by inventorying artifacts, dispatching multi-agent validators, aggregating results, and generating pass/fail reports for phase transitions.
Reviews planning artifacts like requirements, data models, API contracts for gaps in analysis and design phases. Classifies issues by severity for quality gates before proceeding.
Generates Pharaoh tailoring files (id-conventions.yaml, workflows.yaml, artefact-catalog.yaml, checklists/requirement.md) in .pharaoh/project/ from detected-conventions JSON after pharaoh-tailor-detect.