skills.rest
vivainio
vivainioCOMMUNITY
Explore all skills by this author →
GitHub

mspec

Manage spec-driven design workflows by organizing plans and requirements in a `specs/` directory.

Updated Jan 11, 2026
Search Tags:#documentation#workflow automation#feature planning#spec-driven development#requirements management#project handover
One-click install
npx skills add https://github.com/vivainio/agent-skills --skill mspec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mspec
Source: https://github.com/vivainio/agent-skills/tree/main/extra-skills/mspec
Command: npx skills add https://github.com/vivainio/agent-skills --skill mspec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of managing specifications for software features, ensuring that plans and requirements are consistently documented and updated throughout the development lifecycle.

Core Features & Use Cases

  • Spec Creation: Guides the creation of detailed spec.md files for new features.
  • Progress Tracking: Helps identify work-in-progress features by listing specs without a "Shipped" section.
  • Handover Management: Facilitates smooth transitions by generating plan.md with current status and committing it.
  • Use Case: When starting a new feature, use this skill to create a spec.md file, track decisions made during implementation, and generate a handover document when needed.

Quick Start

Use the mspec skill to start a new feature in the 'api' area called 'user-authentication'.

Frequently Asked Questions about mspec

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

FAQPage Schema
How do I manage spec-driven development workflows for software features?▼

Spec-driven development workflows are managed by organizing plans and requirements within a dedicated specs directory. The Skill guides feature initiation, tracks progress via spec status, and facilitates project handovers by generating and committing plan.md files.

What is the best way to track work-in-progress features during requirements management?▼

Requirements management tracks work-in-progress features by listing spec.md files that do not contain a Shipped section. This allows developers to quickly identify which features still require active development and documentation updates.

How do I create detailed specifications for new software features?▼

Specifications for new software features are created using a minimal template to generate spec.md files. The Skill guides the creation process within a two-level hierarchy for spec organization, ensuring requirements are consistently documented.

How do I facilitate project handovers when automating feature planning documentation?▼

Project handovers are facilitated by generating a plan.md file containing the current spec status and committing it to the repository. This ensures smooth transitions by providing the next developer with documented decisions and implementation progress.

Can I organize feature plans using a two-level hierarchy for spec files?▼

Feature plans can be organized using a required two-level hierarchy for spec organization within a dedicated specs directory. This structure ensures that spec.md files are systematically categorized by area and feature name.

Related Skills

Explore More Software Engineering Skills→
langwatchlangwatch
3.5k

plan

Create a feature file with acceptance criteria before implementation.

Official
Intermediate
danielpradilladanielpradilla

prince2-closure-pack

Generate PRINCE2 project closure documentation including acceptance and lessons reports.

Community
Intermediate
oldwinteroldwinter
5

linear-cli

Manage Linear issues, projects, and teams via command-line interface.

Community
Intermediate
kivo360kivo360
1

Orchestrating SPEC-First TDD Development

Orchestrate SPEC-first TDD workflows with SPEC, TEST, CODE, and DOC phases.

Community
Advanced