sk-spec

Guide a four-mode software development workflow from exploration to task breakdown.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ausbru87/mux-addons --skill sk-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sk-spec
Source: https://github.com/ausbru87/mux-addons/tree/main/skills/sk-spec
Command: npx skills add https://github.com/ausbru87/mux-addons --skill sk-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of defining, planning, and breaking down software features according to strict development principles, ensuring clarity and adherence to best practices.

Core Features & Use Cases

  • Explore: Research and gather context for new features.
  • Specify: Create formal feature specifications with requirements and acceptance criteria.
  • Plan: Develop detailed technical implementation plans, including architecture and risk assessment.
  • Tasks: Break down the plan into granular, executable tasks with parallelization markers.
  • Use Case: Kickstart a new feature by having the AI guide you through exploring requirements, writing a formal specification, planning the technical implementation, and finally generating a list of actionable tasks for developers.

Quick Start

Initiate a spec-driven feature by typing /speckit and describing your feature idea.

Frequently Asked Questions about sk-spec

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

FAQPage Schema
What is spec-driven development and how does it structure software engineering workflows?

Spec-driven development structures software engineering into four sequential modes: explore, specify, plan, and task breakdown. It enforces constitutional principles like library-first design and test-first imperatives to generate formal specifications, technical implementation plans, and executable task lists.

How do I create a technical implementation plan from a feature specification?

To create a technical implementation plan, transition into the plan mode after specifying requirements. This develops detailed architecture, assesses technical risks, and enforces strict development mandates including simplicity, anti-abstraction, and integration-first testing before generating executable tasks.

Can I break down a software development plan into granular tasks for parallel execution?

Yes, the task breakdown mode transforms detailed technical implementation plans into granular, executable tasks. It includes explicit parallelization markers and handoff protocols, allowing implementation agents to execute the generated task list efficiently.

Does spec-driven development enforce library-first design and CLI interfaces?

Yes, strict constitutional enforcement mandates library-first design, CLI interfaces, test-first imperatives, simplicity, anti-abstraction, and integration-first testing throughout the entire explore, specify, plan, and task breakdown workflow.

Why use a structured specification workflow for software feature planning instead of ad-hoc methods?

A structured specification workflow automates feature definition and planning according to strict development principles. It ensures clarity by generating formal specifications with acceptance criteria, detailed architecture plans, and actionable developer tasks, preventing ambiguity common in ad-hoc planning.