run-sdlc

Identify SDLC lifecycle phase and recommend next workflow steps for work items.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/tsunami28/MindNova --skill run-sdlc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-sdlc
Source: https://github.com/tsunami28/MindNova/tree/main/.claude/skills/run-sdlc
Command: npx skills add https://github.com/tsunami28/MindNova --skill run-sdlc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams determine where a work item or artifact is in the AI-SDLC lifecycle and identify the correct next step without manually tracing documentation, dependencies, and ownership.

Core Features & Use Cases

  • Lifecycle Navigation: Resolves work items and artifacts, traverses linked relationships, and reports the current SDLC phase.
  • Artifact Graph Analysis: Identifies available and missing lifecycle artifacts such as stories, specifications, ADRs, tests, and documentation.
  • Workflow Guidance: Recommends the appropriate next phase step and owning persona while keeping navigation read-only.
  • Use Case: A product team can provide a story key like MN-42 to understand its current development stage, missing prerequisites, and the recommended next workflow action.

Quick Start

Use the run-sdlc skill to analyze the current lifecycle status and next steps for the provided work item or artifact.

Frequently Asked Questions about run-sdlc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check the current phase of a work item in the SDLC workflow?

To check the current phase of a work item in the SDLC workflow, you can analyze its lifecycle position by traversing linked relationships and reporting its development stage, such as identifying missing prerequisites or required next actions.

What is the best way to identify missing artifacts like specifications and ADRs for a story?

Identifying missing artifacts like specifications and ADRs for a story requires artifact graph analysis, which traverses linked repository artifacts to detect available and missing lifecycle components and report required prerequisites.

How does lifecycle navigation work for linked repository artifacts?

Lifecycle navigation for linked repository artifacts works by performing read-only graph traversal to resolve work items, detect the current SDLC phase, map ownership, and recommend the appropriate next workflow step without modifying the project state.

Can I use this to recommend the next workflow step and owning persona for a story key?

Yes, you can use this to recommend the next workflow step and owning persona for a story key by resolving the item, analyzing the artifact graph, and mapping the current lifecycle position to the appropriate subsequent phase action.

Does SDLC artifact graph analysis require read-only project access?

Yes, SDLC artifact graph analysis requires read-only project access to safely traverse linked relationships, detect phases, and map ownership without modifying the existing development environment or repository artifacts.

When should I not use an automated SDLC workflow navigation approach?

You should not use an automated SDLC workflow navigation approach if your project lacks structured artifact linking or if your delivery scenario operates outside of standard stories, specifications, ADRs, and documentation lifecycle phases.