agile-lifecycle

Plugin agile-lifecycle from marketplace nsalvacao-claude-code-plugins in nsalvacao/nsalvacao-claude-code-plugins. Commands read from the repo's manifest — 1 month ago.

Skills (16)

• ai-lifecycle

  This skill should be used when a project includes AI/ML components and needs guidance on experiment design, model card creation, AI validation, bias and fairness assessment, LLM red-teaming, or drift monitoring configuration. Applies when a user asks to design an AI experiment, plan model validation

• artefact-authoring

  This skill should be used when a user needs to create, fill, or validate a lifecycle artefact using the framework's template library — including selecting the correct template for a phase or gate artefact, filling all mandatory fields, removing guidance comments, and validating against a JSON schema

• backlog-management

  This skill should be used when shaping the product backlog, prioritizing stories, or preparing items for sprint readiness. Triggers when entering Phase 3 (Discovery), transitioning to Phase 4 (Delivery), or when backlog health needs assessment.

• change-control

  This skill should be used when evaluating if a change is incremental or significant, when processing a change request, or when updating the change log. Triggers when scope, requirements, or architecture changes are proposed.

• definition-of-done

  This skill should be used when defining, applying, or updating the Definition of Done. Triggers when Phase 4 is about to start, when a story is declared complete, or when quality standards need to be updated across sprint and release levels.

• evidence-management

  This skill should be used when assembling gate evidence packs, tracking artefact completeness, or managing waivers before any gate review (A–F). Triggers when a phase is approaching its gate or when evidence index needs to be updated.

• gate-checklist

  This skill should be used when conducting a formal gate review (Gates A-F), when validating gate criteria, or when deciding PASS/FAIL/WAIVED for a lifecycle gate.

• lifecycle-tailoring

  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 buildi

• metrics-tracking

  This skill should be used when sprint metrics, quality metrics, AI/ML model metrics, or governance metrics need to be collected, calculated against thresholds, or reported. Triggers when a user asks for a sprint metrics report, wants to check if velocity is healthy, needs an AI monitoring report, or

• operational-readiness

  This skill should be used when preparing for production deployment, assessing operational readiness, or planning the ops transition. Triggers before Gate E (release readiness) or when transitioning to Phase 6.

• phase-contract-enforcement

  This skill should be used when tracking deviations from signed phase contracts, managing scope changes that affect contracts, or escalating contract violations. Triggers when a change request arrives, when a phase is running beyond its contract bounds, or when a gate review reveals contractual non-c

• phase-contract

  This skill should be used when creating a new phase contract at the start of a phase, validating entry criteria before phase work begins, tracking exit criteria progress during a phase, or triggering a gate review when all exit criteria are met. This skill creates and maintains phase contracts; for

• responsibility-flows

  This skill should be used when creating RACI charts, mapping accountability by activity, resolving accountability gaps, or producing the Role-Responsibility Map artefact. Triggers when entering Phase 2 (Architecture) or Phase 3 (Discovery), or when team structure changes during delivery.

• retrospective

  This skill should be used when a full sprint or phase retrospective needs facilitation, when the improvement backlog needs management, or when retrospective action items from a prior sprint need follow-up. This is the primary retrospective skill — sprint-facilitation references it for deep retrospec

• risk-management

  This skill should be used when managing risks, assumptions, clarifications, or dependencies. Triggers when adding new risks, updating risk status, identifying assumptions, or tracking open decisions.

• sprint-facilitation

  This skill should be used when facilitating sprint ceremonies — sprint planning, daily standup, or sprint review. Triggers when a new sprint starts, when a standup is losing focus, or when a sprint review needs stakeholder demo structure. For deep retrospective facilitation or improvement backlog ma

Slash commands (11)

• /agile-lifecycle:agile-artefact-gen

  Generate a lifecycle artefact from template. Without args, lists available templates for current phase.

• /agile-lifecycle:agile-change-request

  Evaluate and log a change request — determines if change is incremental or significant, triggers change control process if needed.

• /agile-lifecycle:agile-gate-review

  Execute a formal gate review. Checks gate criteria, validates artefacts, produces gate-review-report with PASS/FAIL/WAIVED outcome.

• /agile-lifecycle:agile-init

  Initialize agile-lifecycle framework for a new project. Creates lifecycle-state.json, directory structure, and bootstraps Phase 1.

• /agile-lifecycle:agile-metrics-report

  Generate a metrics report for the current phase or overall lifecycle — delivery, quality, product, AI, governance metrics.

• /agile-lifecycle:agile-phase-start

  Start or resume a lifecycle phase. Validates entry criteria, creates phase contract, invokes phase agents.

• /agile-lifecycle:agile-retrospective

  Facilitate a sprint or phase retrospective — what went well, what to improve, action items.

• /agile-lifecycle:agile-risk-update

  Add or update entries in risk register, assumption register, clarification log, or dependency log.

• /agile-lifecycle:agile-sprint-plan

  Plan or review the current sprint — sprint goal, committed backlog, capacity, acceptance criteria.

• /agile-lifecycle:agile-status

  Show current lifecycle status — active phase, gate status, open risks, pending artefacts, and metrics summary.

• /agile-lifecycle:agile-tailoring

  Configure lifecycle tailoring for the project type — SaaS, web, desktop, CLI, AI/ML product. Adjusts gates, artefacts, and phase depth.

Hooks (3)

• PreToolUse

  bash ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/validate-artefact.sh

• PostToolUse

  bash ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/lf-check.sh

• PostToolUse

  bash ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/check-phase-state.sh

Similar plugins