blade-spec

Name: blade-spec
Availability: InStock
Author: tiantien

Convert feature ideas into structured requirements, technical design, and task plans.

Updated Apr 22, 2026

Search Tags:#software engineering #workflow automation #technical design #task decomposition #requirements analysis #spec-driven development

Ready to run

npx skills add https://github.com/tiantien/team-ai-coding-plugin --skill blade-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: blade-spec
Source: https://github.com/tiantien/team-ai-coding-plugin/tree/main/skills/blade-spec
Command: npx skills add https://github.com/tiantien/team-ai-coding-plugin --skill blade-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the guesswork from complex feature development by turning a vague request into a structured, reviewable specification and an execution plan the AI can follow consistently.

Core Features & Use Cases

Requirements analysis: Converts a one-line idea into clear user stories, acceptance criteria, scope boundaries, and assumptions.
Technical design: Maps the approved requirements into module structure, data models, APIs, and implementation decisions.
Task decomposition and execution: Breaks work into ordered tasks, tracks status in files, and supports checkpointed continuation for long-running development.
Use case: A team asks for a new multi-step product feature, and the Skill produces a complete spec, design, task list, and traceable execution flow instead of ad hoc coding.

Quick Start

Tell the blade-spec skill to plan and execute your complex feature request from requirements through implementation.

Frequently Asked Questions about blade-spec

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

FAQPage Schema

How do I turn complex feature ideas into structured technical specs for AI execution?▼

Spec-driven development converts complex feature ideas into structured requirements, technical designs, and ordered task plans, enabling AI-guided software delivery with traceable execution and file-based progress tracking.

What is the best way to break down a large multi-step product feature into an execution plan?▼

Task decomposition breaks work into ordered tasks, tracks status in files, and supports checkpointed continuation for long-running development, ensuring deterministic implementation and resumable execution.

How do I create traceable requirements and technical designs for full-stack engineering workflows?▼

Requirements analysis maps a one-line idea into user stories, acceptance criteria, scope boundaries, and assumptions, then translates approved requirements into module structure, data models, and APIs.

Can I use spec-driven development for large refactors and multi-step product development?▼

Yes, spec-driven development applies to full-stack engineering workflows, large refactors, and multi-step product development that need approvals, traceability, and resumable execution.

Do I need any specific dependencies to run spec-driven validation and phased state tracking?▼

No specific dependencies are required. The skill enforces spec-driven validation, phased state tracking, and file-based progress management internally for deterministic implementation.

When should I not use spec-driven development for software engineering tasks?▼

Spec-driven development is unnecessary for simple, ad hoc coding tasks that do not require approvals, traceability, or phased state tracking across complex multi-step workflows.