SDLC-elicit

Facilitates interactive requirements elicitation for the Objectives phase of an AI-first SDLC project.

122|10|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/pangon/ai-sdlc-scaffold --skill sdlc-elicit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: SDLC-elicit
Source: https://github.com/pangon/ai-sdlc-scaffold/tree/main/.claude/skills/SDLC-elicit
Command: npx skills add https://github.com/pangon/ai-sdlc-scaffold --skill sdlc-elicit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the initial phase of software development by interactively gathering and refining project objectives, ensuring all stakeholders' needs are captured and clearly defined before design begins.

Core Features & Use Cases

  • Interactive Requirements Elicitation: Guides users through defining stakeholders, goals, user stories, requirements, assumptions, and constraints.
  • Artifact Traceability: Establishes and maintains links between different objective artifacts (Stakeholder -> Goals -> User Stories -> Requirements).
  • Gap Analysis: Identifies missing links, uncovered needs, and inconsistencies within the objectives phase artifacts.
  • Status Management: Manages artifact statuses (Draft, Approved) and handles status downgrades upon modification.
  • Use Case: A product manager can use this Skill to collaboratively define the core features of a new application with an AI assistant, ensuring all requirements are documented and traceable from initial stakeholder input.

Quick Start

Initiate an interactive session to define project stakeholders and their associated goals.

Frequently Asked Questions about SDLC-elicit

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

FAQPage Schema
How do I elicit project objectives and requirements interactively for software development?

Requirements elicitation for the Objectives phase involves interactively gathering and refining project objectives, ensuring stakeholder needs are captured. It establishes traceability through a defined chain linking stakeholders, goals, user stories, and requirements.

How do I perform gap analysis on existing software development lifecycle artifacts?

Gap analysis on existing artifacts identifies missing links, uncovered needs, and inconsistencies within the objectives phase. It ensures traceability is maintained throughout the defined chain from stakeholders to requirements.

Can I maintain artifact traceability from stakeholders to requirements during requirements elicitation?

Yes, artifact traceability establishes and maintains links between different objective artifacts, connecting stakeholders to goals, user stories, and requirements. It updates CLAUDE.md and index tables to preserve the defined chain.

How do I manage artifact status downgrades when modifying approved project requirements?

Status management handles artifact statuses like Draft and Approved, automatically processing status downgrades upon modification. This ensures that any changes to approved requirements reset their status for re-evaluation.

What is the best way to document stakeholder goals and user stories before the design phase?

The best way to document stakeholder goals and user stories is through interactive requirements elicitation, which captures and refines project objectives. This approach ensures all assumptions and constraints are documented and traceable.