mspec-new

Create timestamped change directories and README files for the mspec workflow.

4|Updated May 13, 2026
One-click install
npx skills add https://github.com/tubone24/mspec --skill mspec-new
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mspec-new
Source: https://github.com/tubone24/mspec/tree/main/.claude/skills/mspec-new
Command: npx skills add https://github.com/tubone24/mspec --skill mspec-new

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of a new change directory and README file for the mspec workflow, streamlining the initial setup for new changes.

Core Features & Use Cases

  • Automated Directory Creation: Generates a new directory for a change with a unique timestamp and feature name.
  • README Creation: Creates a README file with placeholders for the change request, artifacts, and skipped steps.
  • Workflow Integration: Designed to be used with the mspec CLI for seamless integration into the mspec workflow.

Quick Start

To create a new change, run: /mspec:new <feature-kebab>

Frequently Asked Questions about mspec-new

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

FAQPage Schema
How do I create a change directory and README for the mspec workflow?

To create a change directory and README for the mspec workflow, run the `/mspec:new <feature-kebab>` command. This automates directory generation with a unique timestamp and initializes a README with required sections.

What is the mspec workflow setup process for new changes?

The mspec workflow setup process involves generating a uniquely timestamped directory for your feature and initializing a README file. This Skill automates that bootstrap process, creating placeholders for change requests, artifacts, and skipped steps.

Can I use this directory creation tool with the mspec CLI in Claude Code?

Yes, this directory creation tool is specifically designed to integrate with the mspec CLI within the Claude Code development context. It streamlines the initial setup for new changes by automating directory and README file generation.

What sections are included in the generated README file?

The generated README file includes placeholder sections for the change request, artifacts, and skipped steps. These sections are initialized automatically to ensure your new change directory meets mspec workflow documentation standards.

Do I need any dependencies to automate mspec change directory creation?

No external dependencies are required to automate mspec change directory creation. The Skill operates independently to generate the timestamped directories and README files needed for your workflow management.

Why does workflow automation require unique timestamps for new directories?

Workflow automation requires unique timestamps for new directories to prevent naming collisions and maintain chronological order of changes. This ensures each feature directory remains distinct within the mspec workflow structure.