write-specifications

Generate technical specifications and SPEC.md files using Spec-Driven Development.

4|1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/lushly-dev/afd --skill write-specifications
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-specifications
Source: https://github.com/lushly-dev/afd/tree/main/.claude/skills/write-specifications
Command: npx skills add https://github.com/lushly-dev/afd --skill write-specifications

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of clear, concise, and actionable technical specifications that AI agents can reliably implement, preventing ambiguity and ensuring high-quality software development.

Core Features & Use Cases

  • Spec Authoring: Transforms proposals into structured, agent-consumable specifications following Spec-Driven Development (SDD).
  • Requirement Clarification: Helps resolve ambiguities and conflicting requirements before implementation.
  • Architecture Planning: Maps requirements to architecture using diagrams and contracts.
  • Task Breakdown: Divides specifications into atomic, executable work items.
  • Quality Gates: Ensures spec density and correctness through defined principles.
  • Use Case: When starting a new feature, use this Skill to generate a SPEC.md file that clearly defines the requirements, architecture, and tasks for the development team and AI agents.

Quick Start

Use the write-specifications skill to create a technical plan for a new user authentication feature.

Frequently Asked Questions about write-specifications

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

FAQPage Schema
How do I write a technical specification for AI agent implementation?

To write a technical specification for AI agent implementation, use Spec-Driven Development to transform proposals into structured, agent-consumable specs. This process resolves ambiguities and maps requirements to architecture, ensuring AI agents can reliably execute the defined tasks.

What is Spec-Driven Development and when do I need it for software planning?

Spec-Driven Development (SDD) is a methodology that generates clear technical specifications before implementation. You need SDD when starting a new feature to prevent ambiguity, map architecture, and break down tasks into atomic work items for development teams and AI agents.

How to break down technical specifications into executable tasks for AI agents?

To break down technical specifications into executable tasks, apply SDD methodology to divide specifications into atomic work items. This ensures each task is structured and agent-consumable, allowing AI agents to reliably implement the defined software requirements.

Can I use this to generate a SPEC.md file for my new software feature?

Yes, you can generate a SPEC.md file for a new software feature. It authorizes high-quality technical specifications that clearly define requirements, architecture plans, and task breakdowns, creating an actionable reference for both development teams and AI agents.

What's the best way to resolve conflicting requirements before writing technical documentation?

The best way to resolve conflicting requirements is through structured requirement clarification during technical spec authoring. This identifies and resolves ambiguities early, ensuring the resulting SPEC.md file contains clear, actionable, and correct instructions.

How does architecture planning work when authoring technical specs?

Architecture planning in technical spec authoring works by mapping resolved requirements to system architecture using diagrams and contracts. This ensures the technical specifications align with structural constraints before breaking down the work into executable tasks.