spec

Name: spec
Availability: InStock
Author: sanskarbasnet

Convert an active intent into a structured spec document with seven sections.

1|Updated May 4, 2026

Search Tags:#workflow #documentation #specification #engineering #intent #design-doc #pursue

Ready to run

npx skills add https://github.com/sanskarbasnet/fstack --skill spec-sanskarbasnet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/sanskarbasnet/fstack/tree/main/spec
Command: npx skills add https://github.com/sanskarbasnet/fstack --skill spec-sanskarbasnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts an active intent into a formal, structured spec document that defines goals, inputs, outputs, behavior, edge cases, test matrix, and scope, enabling reliable implementation.

Core Features & Use Cases

Load design doc to align the spec with the chosen design.
Scan the codebase for context and anchor the spec in existing abstractions.
Draft seven sections: Goal, Inputs, Outputs, Behavior, Edge cases, Test matrix, Out of scope.
Write the spec to docs/specs/<slug>.md and attach to the active intent.

Quick Start

Invoke /spec on an active intent to generate docs/specs/<slug>.md and attach the result to the intent.

Frequently Asked Questions about spec

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

FAQPage Schema

How do I turn an engineering intent into a structured spec document?▼

To turn an engineering intent into a spec document, invoke the /spec workflow on your active intent. It scans the codebase, loads optional design docs, and drafts a seven-section specification to docs/specs/<slug>.md for implementation guidance.

What sections should a feature specification include for non-trivial engineering tasks?▼

A feature specification should include Goal, Inputs, Outputs, Behavior, Edge cases, Test matrix, and Out of scope sections. This structure ensures reliable implementation by defining boundaries and anchoring specifications in existing codebase abstractions.

How do I generate a test matrix from a design doc for a new feature?▼

To generate a test matrix from a design doc, load the design doc during the specification workflow. The process drafts the behavior and edge cases, automatically producing a structured test matrix that attaches to the active intent.

Can I anchor new specifications to existing codebase abstractions automatically?▼

Yes, you can anchor new specifications to existing abstractions automatically. The workflow scans your codebase for context before drafting the specification, ensuring the generated document aligns with your current architecture and design.

When do I need a formal specification document for software engineering?▼

You need a formal specification document for non-trivial features requiring clear goals, inputs, outputs, and defined behavior. Generating a spec prevents ambiguity by explicitly listing edge cases, a test matrix, and out-of-scope boundaries before implementation begins.