fsd:create-spec

Generate technical implementation specs from codebase analysis and Linear issues.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/fixpoint-labs/flow-state-dev --skill fsd-create-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fsd:create-spec
Source: https://github.com/fixpoint-labs/flow-state-dev/tree/main/.agents/skills/create-spec
Command: npx skills add https://github.com/fixpoint-labs/flow-state-dev --skill fsd-create-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires linear-client, code-analysis, web-search, document-automation, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps generate detailed implementation specs for software development tasks, reducing ambiguity and improving collaboration.

Core Features & Use Cases

  • Automated Specification Research: Collects data from web sources, codebase patterns, and existing code for issue analysis.
  • Versioned Documentation: Publishes specs as versioned documents for review and integrates with Linear issues for synchronization.
  • Multi-Agent Collaboration: Utilizes multiple sub-agents for code analysis, dependency checks, and documentation scoping.
  • Necessity Check: Determines if the implementation is necessary, offering alternatives if not.
  • Spec Documentation: Provides a structured format for the spec document with key sections like Overview, Technical Design, Implementation Sequence, etc.

Quick Start

Generate a specification for an issue with ID 'FSD-142' by running the skill: generate_spec_for_issue "FSD-142"

Frequently Asked Questions about fsd:create-spec

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

FAQPage Schema
How do I generate technical implementation specs for software projects?

Technical implementation specs are generated using multi-agent workflows that research codebase patterns and web sources, integrate with Linear for tracking, and output structured documentation for synchronized review and collaboration.

How do I create a specification for a Linear issue?

Creating a specification for a Linear issue involves triggering an automated workflow with the issue ID, which collects codebase and web data to publish a versioned spec document synchronized with the Linear issue.

Do I need a connected codebase to generate technical specs?

Generating technical specs requires integration with a codebase and a Linear instance, because the workflow uses code analysis to evaluate existing patterns and determine implementation necessity.

What is the best way to structure a technical spec for issue implementation?

The best way to structure a technical spec for issue implementation is using a structured documentation format with key sections like Overview, Technical Design, and Implementation Sequence, enhanced by automated codebase research.

Can automated specification research determine if an implementation is necessary?

Automated specification research can determine if an implementation is necessary by utilizing multiple sub-agents for code analysis and dependency checks, offering alternatives if the implementation is deemed unnecessary.