functional-spec-authoring

name	functional-spec-authoring
description	Guide iterative authoring of functional specifications as Azure DevOps work item hierarchies (Epic → Feature → User Story). Use for business requirement capture, scope definition, acceptance criteria, and approval readiness.
argument-hint	Describe the business need or feature idea to explore, or provide an existing Epic ID to refine.

Functional Spec Authoring

When to Use

• Define a new capability as Epic → Feature → User Story
• Iterate requirements before technical spec
• Prepare a spec for review or approval

Required Caller Configuration

The calling agent must provide the Azure DevOps organization, project, and any other target-specific values needed for MCP calls. This skill defines generic field, template, and workflow rules only; do not hardcode repository-specific Azure DevOps targets here.

Hierarchy

Level	Purpose	Azure DevOps type
Epic	WHY — business justification, strategic goal	Epic
Feature	WHAT — capability scope, boundaries	Feature (child of Epic)
User Story	WHAT — user-facing behavior, criteria	User Story (child of Feature)

Tasks/Bugs are implementation, not functional spec.

Field Model

Type	Description field	Acceptance Criteria field
Epic