gsd-spec-phase

Define software phase requirements via structured questioning and ambiguity scoring.

Updated Apr 22, 2025
One-click install
npx skills add https://github.com/mcampbellr/.dotfiles --skill gsd-spec-phase-mcampbellr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-spec-phase
Source: https://github.com/mcampbellr/.dotfiles/tree/main/claude/.claude/skills/gsd-spec-phase
Command: npx skills add https://github.com/mcampbellr/.dotfiles --skill gsd-spec-phase-mcampbellr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you clarify and quantify the deliverables of software development phases, reducing ambiguity and improving project alignment.

Core Features & Use Cases

  • Structured Questioning: Guides you through a structured process using Socratic questioning.
  • Ambiguity Scoring: Evaluates clarity based on weighted dimensions, guiding refinement.
  • Automatic Documentation: Automatically produces a SPEC.md file with validated requirements.

Quick Start

To create a SPEC for a development phase, run gsd-spec-phase <phase> [--auto] [--text].

Frequently Asked Questions about gsd-spec-phase

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

FAQPage Schema
How do I define clear software phase requirements and reduce ambiguity?

To define clear software phase requirements, use structured Socratic questioning and ambiguity scoring to quantify deliverables, generating a validated SPEC.md file for project alignment.

What is the best way to document deliverables for a specific development phase?

The best way to document phase deliverables is running a script-based command like `gsd-spec-phase <phase>` to automatically produce a SPEC.md file containing validated and refined requirements.

How does ambiguity scoring work for project management specifications?

Ambiguity scoring evaluates specification clarity across weighted dimensions, identifying vague areas in your project management requirements to guide refinement and ensure quantifiable deliverables.

Do I need specific context files to generate a SPEC.md for my project?

Yes, generating a SPEC.md requires specific context files and script-based execution tools to operate, targeting administrative and technical roles within your project team for accurate phase planning.

Can I automate the specification process without manual questioning?

Yes, you can automate the specification process by running the command with the `--auto` flag, bypassing manual Socratic questioning to produce requirements documentation directly.