spec-authoring

Write and push Spec Driven Development documents in MySpec platform formats.

Updated Sep 12, 2026
One-click install
npx skills add https://github.com/myspecs/claude-plugins --skill spec-authoring-myspecs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-authoring
Source: https://github.com/myspecs/claude-plugins/tree/main/plugins/myspec-mcp/skills/spec-authoring
Command: npx skills add https://github.com/myspecs/claude-plugins --skill spec-authoring-myspecs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing specification documents that pass the MySpec platform's reviewers requires exact section skeletons, id conventions, and quality rules; this Skill produces constitution, requirements, solution, tasks, and change proposal documents that match those formats precisely. ## Core Features & Use Cases - Greenfield spec bundles: Generate constitution.md, requirements.md, solution.md, and tasks.md with EARS+ acceptance criteria, FR/NFR ids, and mandatory Mermaid diagrams. - Brownfield change documents: Author MySpec change proposals with AR/BR/CR requirements deltas, or OpenSpec-compatible proposals, delta specs, designs, and tasks. - Platform sync: Upload new spec files or update existing ones on MySpec via the myspec MCP server, handling version conflicts and path rules. - Use Case: A team starting a new product asks for a full spec bundle; the Skill gathers decisions, writes all four documents in the platform's exact formats, self-reviews them against reviewer rules, and pushes them to the MySpec project. ## Quick Start Ask the assistant to write a constitution, requirements, solution, and tasks bundle for your project and push it to MySpec.

Frequently Asked Questions about spec-authoring

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

FAQPage Schema
How do I write requirements with EARS acceptance criteria?▼

EARS+ acceptance criteria use patterns like WHEN <event> THEN the system SHALL <response>, with variants for conditions, states, and error handling. Each functional requirement gets testable, technology-neutral criteria under an Acceptance Criteria section.

What documents does a MySpec greenfield spec bundle contain?▼

A greenfield bundle contains constitution.md, requirements.md, solution.md, and tasks.md, written in that order under specs/<bundle>/. Requirements must obey the constitution, the solution uses only approved technology, and every FR gets at least one task.

How do I write a brownfield change proposal for an existing codebase?▼

A MySpec brownfield bundle has proposal.md plus a requirements delta using AR (add), BR (remove), and CR (change) entries grouped per module. Every claim must be grounded in code you actually read, and BR entries require a file:line reference.

Can I upload OpenSpec change files to MySpec through MCP?▼

Proposal, design, and tasks files can be uploaded, but new capability delta specs at openspec/changes/<id>/specs/<capability>/spec.md are four levels deep and exceed the three-level upload limit. Keep new deltas local for the OpenSpec CLI; existing ones can still be updated.

Why does the MySpec reviewer reject my requirements document?▼

Common causes are architecture prescriptions or product names (requirements must be technology-neutral), FRs without testable acceptance criteria, NFRs lacking measurable targets or priorities, and Data or Integration sections exceeding five bullets.

Does spec-authoring work without the myspec MCP server?▼

Documents can be written locally without the MCP server, but pushing them to a MySpec project requires the myspec MCP server configured via the setup skill. Upload and update operations use tools like upload_spec_file and update_spec_file.