spec

Interview users to create spec.md files with requirements and acceptance criteria.

1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/nbdesai1992/software-factory --skill spec-nbdesai1992
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/nbdesai1992/software-factory/tree/main/factory/skills/spec
Command: npx skills add https://github.com/nbdesai1992/software-factory --skill spec-nbdesai1992

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to rapidly create, update, and maintain development specifications by guiding an interview-driven process and enforcing consistent templates.

Core Features & Use Cases

  • Interview-driven specification creation: gathers requirements, scope, and acceptance criteria from stakeholders.
  • Trajectory logging and session management: records the spec lifecycle for audit and replay.
  • Template-driven outputs: produces a structured spec.md with IDs, acceptance criteria, and scope boundaries.
  • Modes: CREATE, UPDATE, SHOW operations to manage the spec lifecycle.

Quick Start

Initiate a CREATE session to interview the user and generate a draft spec.md with IDs and acceptance criteria.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I draft precise project specs from stakeholder interviews?

Drafting project specs from interviews is handled through an interactive session that gathers requirements and produces a structured spec.md file with scope boundaries and acceptance criteria.

What is the best way to track requirements and scope boundaries for new product initiatives?

Tracking requirements for product initiatives is achieved by generating a spec.md with unique IDs, acceptance criteria, and trajectory logging to record the specification lifecycle for audit.

How do I update an existing feature specification without losing original requirements?

Updating an existing feature specification uses an UPDATE mode to modify the spec.md while maintaining trajectory logging and session management to preserve the lifecycle history.

Can I use interview-driven specification templates for orchestrated development workflows?

Interview-driven specification templates are explicitly designed for orchestrated development workflows to manage spec lifecycles when creating or updating major changes and new work items.

Does the specification generation process support session replay and audit?

The specification generation process supports session replay and audit through trajectory logging, which records the entire spec lifecycle during the CREATE, UPDATE, and SHOW operations.