skills.rest
sandsower
sandsowerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec

Shapes vague ideas and tickets into approved lightweight product specs.

10|Updated May 12, 2026
Search Tags:#requirements#discovery#interview#prd#product spec#workflow gate#scope classification
One-click install
npx skills add https://github.com/sandsower/beislid --skill spec-sandsower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/sandsower/beislid/tree/main/skills/spec
Command: npx skills add https://github.com/sandsower/beislid --skill spec-sandsower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump from a vague idea or ticket straight into code, producing misaligned implementations. This Skill enforces a product-requirements gate that interviews the user, clarifies scope and acceptance criteria, and produces an approved lightweight spec before any implementation design begins. ## Core Features & Use Cases - Structured Discovery Interview: Asks targeted questions one at a time, grounded in codebase evidence, to resolve unknowns about the problem, desired behavior, and success criteria. - Approved Spec Artifact: Produces a standardized spec template (problem statement, current/desired state, user stories, key decisions, out of scope) plus an optional work-contract-v1 section with scope classification for downstream routing. - Lifecycle Integration: Runs repo-configured spec_approved lifecycle actions (artifact writes, tracker posts, CLI hooks) and routes approved specs to blueprint, break-spec, or spec_refinement based on scope classification. - Use Case: A developer receives a vague ticket like "improve onboarding". The Skill explores the codebase, interviews the user about target users and success metrics, proposes product directions, and delivers an approved spec ready for implementation design. ## Quick Start Ask the agent to spec out the new onboarding improvement ticket before any implementation begins.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I write a lightweight product spec before coding?▼

Invoke the spec skill with a phrase like "spec this out" and it interviews you about the problem, desired behavior, and success criteria. It then proposes product directions and produces an approved spec using a standard template covering problem statement, user stories, key decisions, and scope.

What is the difference between spec and blueprint skills?▼

Spec handles product requirements: what to build, for whom, and why. Blueprint handles implementation design after requirements are clear. Spec explicitly blocks implementation details and routes approved specs to blueprint or break-spec based on scope classification.

Can the spec skill post approved specs to a ticket tracker?▼

Yes, when the repo's .beislid/workflow.md configures spec_approved lifecycle actions, the skill can write spec artifacts to files, post the approved spec body to a tracker, or run CLI hooks. Each action respects approval prompts and action-policy gates.

When should I not use the spec skill?▼

Skip spec when requirements are already clear and you need implementation design (use blueprint), when breaking an approved spec into phases (use break-spec), or when writing code directly. Spec is the product-requirements gate, not a design or coding tool.

What is a work contract in the spec output?▼

A work-contract-v1 section captures Kind, Status, Problem, Acceptance Outcomes, and a scope_classification (atomic, single_pr, multi_slice, project, or unknown). Downstream automation uses this classification to route work and determine whether extra human approval is required.

Related Skills

Explore More Product & Management Skills→
unblockedunblocked
13

headless-enrich-ticket

Gather context and attach structured enrichment documents to issue tracker tickets.

Official
Advanced
arthur-debertarthur-debert

to-tickets

Break specs and ADRs into epic and work stream tracker issues.

Community
Advanced
inkeepinkeep
3.9k

review-a-design

Reviews design proposals, specs, and ADRs for soundness and emits ranked evidence-backed findings.

Official
Advanced
opsMachineopsMachine
1

implement-direct

Implement approved specs directly without test-driven development.

Official
Advanced