functional-spec

Generates a Functional Requirements Specification document with use cases, business rules, and acceptance criteria.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/tektonlabs/ai-software-design --skill functional-spec-tektonlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: functional-spec
Source: https://github.com/tektonlabs/ai-software-design/tree/main/.claude/skills/define/functional-spec
Command: npx skills add https://github.com/tektonlabs/ai-software-design --skill functional-spec-tektonlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams moving from a signed strategic intake to development often lack a precise, traceable definition of what the system must do, causing AI agents and developers to invent behavior. This Skill produces a structured Functional Requirements Specification (FRS) that closes that gap. ## Core Features & Use Cases - Structured FRS Generation: Produces a complete FRS with system overview, user roles, functional requirements in FR-XXX format, use cases in UC-XXX format, business rules, and acceptance criteria in Given-When-Then form. - Traceability & Governance: Maps every requirement back to the signed Strategic Intake document, enforces validation rules, and requires BSA sign-off before downstream phases can start. - Use Case: After your Strategic Intake is approved, run this Skill to draft the full functional specification for a customer portal, including role definitions, per-feature requirements, and out-of-scope items, ready for BSA approval. ## Quick Start Ask the agent to generate the Functional Requirements Specification for your project now that the Strategic Intake document is signed.

Frequently Asked Questions about functional-spec

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

FAQPage Schema
How do I write a functional requirements specification for a software project?▼

Provide the signed Strategic Intake document, user roles, in-scope features, and business rules. The Skill generates a structured FRS with FR-XXX requirements, use cases, acceptance criteria, and traceability back to the intake document.

What format should functional requirements follow?▼

Each requirement uses the format "The system shall..." with an FR-[Feature Code]-[###] identifier, a priority of Must Have, Should Have, or Won't v1, and at least one Given-When-Then acceptance criterion.

What must exist before generating a functional specification?▼

The Strategic Intake document from Phase 1 must exist at documentation/01-understand/strategic-intake.md and be signed. The Skill blocks execution and reports the missing prerequisite if it is not signed.

Who approves a functional requirements specification?▼

The Business Systems Analyst (BSA) holds final approval authority and must sign the document. The Business Sponsor confirms business alignment, and the Tech Lead provides a conditional feasibility review.

Why does FRS generation fail validation?▼

Validation fails if prerequisites are unsigned, the document is not at its canonical path, placeholder text remains, sections are empty, the FRS-[###] document ID is malformed, or cross-references point to unsigned documents.