skills.rest
maragudk
maragudkOFFICIAL
Explore all skills by this author →
WebsiteGitHub

spec

Create and update a living product spec at docs/spec.md.

27|2|Updated Mar 27, 2026
Search Tags:#planning#documentation#requirements#spec#brainstorm#stakeholders#product-spec
One-click install
npx skills add https://github.com/maragudk/fabrik --skill spec-maragudk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/maragudk/fabrik/tree/main/skills/spec
Command: npx skills add https://github.com/maragudk/fabrik --skill spec-maragudk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The spec helps teams create and iterate on a living product specification (docs/spec.md), ensuring alignment and clarity across stakeholders and throughout a project lifecycle.

Core Features & Use Cases

  • Structured workflow for capturing objectives, users, features, constraints, and success criteria.
  • Supports brainstorming, approvals, and incremental updates to the spec.
  • Proactive nudges to capture decisions in the spec during conversations.

Quick Start

Ask me to create or update docs/spec.md and I will guide you through drafting the spec.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I create a living product spec for a new software project?▼

To create a living product spec, draft a document at docs/spec.md capturing objectives, users, features, non-goals, constraints, and success criteria. This ensures alignment across stakeholders throughout the project lifecycle.

What sections should be included in a product specification document?▼

A standard product specification document includes Objective, Users, Features, Non-goals, Constraints, Success criteria, and Open questions, along with frontmatter metadata to maintain a structured and clear project scope.

How do I capture product decisions during brainstorming with stakeholders?▼

Capture product decisions during brainstorming by using proactive nudges to record choices directly in docs/spec.md. This maintains a living specification that evolves with ongoing stakeholder conversations.

Can I update my product requirements incrementally as the project evolves?▼

Yes, you can update product requirements incrementally as the project evolves. The spec supports approvals and ongoing updates, allowing teams to maintain alignment by modifying docs/spec.md during development.

What is the best way to maintain alignment on project features across teams?▼

The best way to maintain alignment on project features is by maintaining a living product spec at docs/spec.md. It captures shared objectives, non-goals, and open questions to ensure clarity across all stakeholders.

Related Skills

Explore More Product & Management Skills→
alessioroberto82alessioroberto82

scope

Gather requirements and define project scope for new features.

Community
Intermediate
qa-amanqa-aman
19

pilot-debrief

Synthesize pilot observations into structured debrief reports and spec updates.

Community
Advanced
hlhr202hlhr202
51

conductor-newTrack

Generate spec.md and plan.md files for new Conductor tracks.

Community
Advanced
MysMonMysMon
2

interview

Extract goals, constraints, and success criteria through structured interview phases.

Community
Advanced