build-spec

Guide planning sessions to produce locked SPEC.md, UI_PLAN.md, and CONTRACT.md.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/narduk-enterprises/myboat --skill build-spec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-spec
Source: https://github.com/narduk-enterprises/myboat/tree/main/.github/skills/build-spec
Command: npx skills add https://github.com/narduk-enterprises/myboat --skill build-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides a new site or product through the decisions required to lock SPEC.md, UI_PLAN.md, and CONTRACT.md before design or implementation.

Core Features & Use Cases

  • Structured intake that captures scope, users, flows, content rules, and acceptance criteria.
  • Guidance to produce three locked artifacts: SPEC.md, UI_PLAN.md, and CONTRACT.md.
  • Clear handoff and decision-tracking to surface blockers, assumptions, and resolutions.

Quick Start

Kick off a planning session to convert a vague idea into locked SPEC.md, UI_PLAN.md, and CONTRACT.md.

Frequently Asked Questions about build-spec

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

FAQPage Schema
How do I turn a vague product idea into a locked specification before design?▼

A locked specification requires capturing scope, users, flows, content rules, and acceptance criteria to finalize SPEC.md, UI_PLAN.md, and CONTRACT.md before design or implementation begins.

What decisions are required to finalize requirements and launch acceptance criteria?▼

Finalizing requirements and launch acceptance involves guiding decisions across discovery, routes, content, integrations, SEO, trust, and launch acceptance to lock the project planning artifacts.

How do I document project assumptions and blockers during planning sessions?▼

Document project assumptions and blockers during planning sessions using structured intake and decision-tracking to surface blockers, assumptions, and resolutions for clear handoff.

Can I use this specification workflow for a new site with external integrations?▼

Yes, this specification workflow supports new sites with external integrations by guiding decisions specifically across integrations, routes, content, and SEO within the planning scope.

What is the best way to structure a UI plan and contract for product handoff?▼

The best way to structure a UI plan and contract for handoff is to produce locked UI_PLAN.md and CONTRACT.md artifacts that contain clearly defined decisions, assumptions, and resolutions.