spec/create

Coordinate collaborative specification creation through a five-step discovery-to-polish process.

5|3|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/NexusSema/omg-marketplace --skill spec-create-nexussema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec/create
Source: https://github.com/NexusSema/omg-marketplace/tree/main/plugins/sdlc/skills/spec/create
Command: npx skills add https://github.com/NexusSema/omg-marketplace --skill spec-create-nexussema

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams struggle to capture complex requirements in a consistent format; this skill provides a guided, collaborative workflow to produce high-quality specifications.

Core Features & Use Cases

  • Micro-file architecture for modular steps
  • Just-in-time loading of step content to minimize context
  • Enforced sequential process with explicit user approvals
  • Revision history and frontmatter-driven progress

Quick Start

Begin a spec session and follow guided prompts to complete discovery, scope, build, cross-reference, and polish.

Frequently Asked Questions about spec/create

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

FAQPage Schema
How do I collaboratively create technical specifications with versioning and progress tracking?

Collaborative specification creation is guided through a strict five-step process—discover, scope, build, cross-reference, and polish—capturing decisions and enforcing sequential progress with explicit user approvals.

What is the best way to structure complex requirements into a consistent format?

Structuring complex requirements is handled by applying a guided workflow that uses micro-file architecture and just-in-time content loading to produce high-quality, modular specifications.

How does frontmatter-driven documentation work for requirement tracking?

Frontmatter-driven documentation tracks progress and satisfies change tracking requirements by capturing auditable iterations and preserving user control throughout the specification workflow.

Can I use this specification workflow for team collaboration without losing decision history?

Team collaboration is supported by enforcing a sequential process that captures decisions at every step, maintaining revision history and frontmatter-driven documentation for fully auditable iterations.

What are the limitations of enforcing a strict five-step specification process?

The strict five-step process requires explicit user approvals at each phase, meaning you cannot skip stages like discovery or cross-referencing, ensuring all specifications meet structural completeness before final polish.

Do I need prior documentation experience to scope and build project specifications?

No prior documentation experience is needed to scope and build specifications, as the workflow provides just-in-time guided prompts for subject discovery, scoping, and building to structure input automatically.