Verified:GitHub

spec-write

Create and maintain FR/spec documentation with bimodal frontmatter and validation.

6|Updated Mar 19, 2026

Search Tags:#documentation #workflow-automation #feature-requirements #milestone-attachment #spec-write #fr-frontmatter #tracker-integration

Ready to run

npx skills add https://github.com/nesquikm/dev-process-toolkit --skill spec-write-nesquikm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-write
Source: https://github.com/nesquikm/dev-process-toolkit/tree/main/plugins/dev-process-toolkit/skills/spec-write
Command: npx skills add https://github.com/nesquikm/dev-process-toolkit --skill spec-write-nesquikm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Spec Write skill guides users through creating, updating, and validating feature-spec frontmatter and FR files across multiple FRs, ensuring consistent structure, traceability, and integration with tracker workflows.

Core Features & Use Cases

Per-FR frontmatter scaffolding and per-FR file creation under specs/frs with bimodal identity handling (tracker-mode IDs or short ULIDs).
AC prefix generation, post-write shape validation, and proactive checks like workspace binding and milestone attachment.
Supports both tracker-mode and mode: none workflows, including importing from trackers, avoiding duplicates, and enforcing gating rules.

Quick Start

Invoke /dev-process-toolkit:spec-write to begin drafting and updating FR specifications across all required sections.

Frequently Asked Questions about spec-write

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

FAQPage Schema

How do I automate feature requirement spec creation across multiple feature requests?▼

To create feature requirement specs across multiple feature requests, you scaffold per-FR frontmatter and generate files under specs/frs. This enforces bimodal identity rules, generates AC prefixes, and validates post-write shapes to maintain traceability and consistency across documentation.

What is bimodal identity handling in feature spec frontmatter?▼

Bimodal identity handling in feature spec frontmatter allows identifiers to function in two modes: using tracker-mode IDs for integrated workflows or generating short ULIDs for mode:none workflows. This ensures consistent spec traceability regardless of external tracker dependencies.

How do I validate feature spec frontmatter after writing requirements and technical specs?▼

Validating feature spec frontmatter after writing requirements involves applying post-write shape validation. This verifies that frontmatter conforms to defined rules, ensuring milestone attachments and workspace bindings align correctly with the generated feature specifications.

Does feature spec documentation work without a tracker integration?▼

Feature spec documentation works without tracker integration by utilizing mode:none workflows. This configuration uses short ULIDs instead of tracker-mode IDs for feature request identification, enabling spec creation and maintenance independently of external tracker systems.

What's the best way to maintain testing specs and planning milestones across multiple FRs?▼

The best way to maintain testing specs and planning milestones across multiple FRs is through automated end-to-end documentation workflows. These workflows enforce frontmatter shapes, generate acceptance criteria prefixes, and integrate workspace bindings with milestone attachments to ensure consistency and traceability.

Why does spec generation require workspace binding and milestone attachment checks?▼

Spec generation requires workspace binding and milestone attachment checks to enforce proactive consistency and traceability across feature requests. These checks ensure that generated frontmatter aligns with bimodal identity rules and tracker gating rules, preventing duplicate imports and structural misalignment.