requirements

Guide stakeholder sessions to document software requirements and draft specifications.

2|Updated Feb 6, 2026

Search Tags:#planning #specification #requirements #discovery #process #stakeholders #gathering

Ready to run

npx skills add https://github.com/ashtonian/llm-init --skill requirements-ashtonian

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements
Source: https://github.com/ashtonian/llm-init/tree/main/templates/.claude/skills/requirements
Command: npx skills add https://github.com/ashtonian/llm-init --skill requirements-ashtonian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interactive requirement gathering to produce clear, actionable technical specifications by guiding conversations with stakeholders and consolidating input into a formal document.

Core Features & Use Cases

Structured Discovery Phases that guide questions and capture outcomes
Iterative scope definition and decision logging to prevent scope creep
Draft Specification Output suitable for docs and downstream planning

Quick Start

Initiate an interactive session with stakeholders to begin gathering requirements and generate a draft specification.

Frequently Asked Questions about requirements

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

FAQPage Schema

How do I gather requirements from stakeholders to produce a clear technical specification?▼

To gather requirements and produce a technical specification, you can run interactive discovery sessions that guide stakeholders through structured phases, capturing decisions and drafting a formal specification document ready for downstream planning.

What is the best way to prevent scope creep during requirements discovery and specification drafting?▼

Preventing scope creep during requirements discovery requires iterative scope definition and structured decision logging throughout the session, ensuring every addition is evaluated and recorded against the agreed project boundaries.

How does an automated requirement discovery process handle edge cases and design decisions?▼

An automated requirement discovery process handles edge cases and design decisions by enforcing a phase-based workflow that explicitly prompts stakeholders to identify edge scenarios, record design choices, and consolidate them into a draft specification.

Can I use interactive requirement gathering for early planning and engineering specification drafts?▼

Yes, interactive requirement gathering is designed for product teams and engineers during early planning, guiding conversations to converge on a clear scope and outputting a formal draft specification suitable for documentation.

What steps are involved in leading a requirements workshop to draft a formal specification?▼

Leading a requirements workshop to draft a formal specification involves guiding stakeholders sequentially through discovery, scope definition, design decisions, edge case analysis, and finalizing a draft specification output for docs.

dtsong

intake-skill

Transform natural language project descriptions into structured engagement briefs.

Community

Advanced

okwinds

prd-to-engineering-spec

Transform a PRD into an implementation-ready engineering specification with architecture, data modeling, API design, security, deployment, and testing.

Community

Advanced