skills.rest
marsley01
marsley01COMMUNITY
Explore all skills by this author →
WebsiteGitHub

vc-generate-spec

Generates plain-language product-discovery SPEC requirements documents from research findings and user intent.

2|Updated Sep 15, 2025
Search Tags:#planning#documentation#requirements#acceptance criteria#user stories#spec#product discovery
One-click install
npx skills add https://github.com/marsley01/Marsley-Portfolio-Web --skill vc-generate-spec-marsley01
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vc-generate-spec
Source: https://github.com/marsley01/Marsley-Portfolio-Web/tree/main/.agents/skills/vc-generate-spec
Command: npx skills add https://github.com/marsley01/Marsley-Portfolio-Web --skill vc-generate-spec-marsley01

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It turns scattered research findings and user brainstorms into a single reviewable requirements document, so users can confirm what will be built before any approach or code is chosen. ## Core Features & Use Cases - SPEC Generation: Produces a structured requirements artifact with canonical sections including Summary, User Stories, Acceptance Criteria, and Open Questions. - Program-Level SPECs: Supports umbrella SPECs that govern multi-phase programs via a dedicated template. - Test-Grounded Acceptance Criteria: Every criterion carries a proven-by test scenario and verification strategy, banning vacuous-green outcomes. - Use Case: After researching a new feature, invoke this skill to write a SPEC the user reviews and approves before INNOVATE and PLAN phases begin. ## Quick Start Ask the agent to generate a SPEC for your feature idea based on the completed research findings and your stated intent.

Frequently Asked Questions about vc-generate-spec

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

FAQPage Schema
How do I write a product requirements document for user review?▼

Use this skill to generate a SPEC with canonical sections: Summary, User Stories, Behavioral Outcomes, Flow Diagram, Acceptance Criteria, Out of Scope, Constraints, Open Questions, and Background. It writes in plain language without file paths, library names, or code so non-engineers can review it.

What should acceptance criteria in a requirements doc include?▼

Each acceptance criterion states an observable outcome plus two annotations: a proven-by test scenario and a strategy of Fully-Automated, Hybrid, or Agent-Probe. Criteria must be grounded in research test-context discovery, with a maximum of 20 per SPEC.

When is a SPEC required before planning?▼

A SPEC is required for all non-trivial work before INNOVATE or PLAN begins. It consumes research findings and user intent, and planning cannot start until Open Questions are resolved or backlogged.

Can a SPEC be edited after planning starts?▼

No. Once INNOVATE or PLAN begins, the SPEC is frozen. Scope gaps discovered later are recorded in the phase report under a SPEC Gaps heading plus a backlog note, never as edits to the original SPEC.

How do phase programs handle SPECs?▼

A phase program writes one umbrella SPEC during the outer loop using the program-spec template, and it governs every inner phase. The inner loop never writes per-phase SPECs.

Related Skills

Explore More Product & Management Skills→
team-attentionteam-attention
171

specify

Interview teams to produce DRAFT.md and PLAN.md work plans.

Official
Advanced
ribatsheporibatshepo

spec-analyzer

Extract requirements, dependencies, and acceptance criteria from specifications.

Community
Advanced
andregusman-raizandregusman-raiz
19

spec-writer

Generate standardized technical SPEC documents for features, issues, and refactors.

Community
Intermediate
chohra-medchohra-med
28

spec-harness-tickets

Convert ticket tracker issues and ad-hoc plans into structured spec documents.

Community
Advanced