skills.rest
timsvoice
timsvoiceCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

specimin-spec

Convert natural language feature requests into structured draft specifications.

Updated Nov 7, 2025
Search Tags:#requirements#spec#product-management#user-stories#acceptance-criteria
One-click install
npx skills add https://github.com/timsvoice/specimin --skill specimin-spec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specimin-spec
Source: https://github.com/timsvoice/specimin/tree/main/.claude-plugin/skills/specimin-spec
Command: npx skills add https://github.com/timsvoice/specimin --skill specimin-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, git, and includes scripts (resource) components.

What problem does it solve?

Converts natural language feature requests into concrete, testable specifications.

Core Features & Use Cases

  • Requirements capture: translate user stories into acceptance criteria.
  • Iterative refinement: asks clarifying questions to remove ambiguity.
  • Specification export: writes spec to repo for review.

Quick Start

Describe your feature, then run the spec generator to craft a draft spec.

Frequently Asked Questions about specimin-spec

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

FAQPage Schema
How do I convert user stories into acceptance criteria and product specs?▼

Acceptance criteria translate user stories into testable conditions. This Skill converts natural language feature requests into structured specifications by guiding you through iterative clarification stages, capturing requirements, and generating a draft spec with acceptance criteria and workflow artifacts for review.

Can I create a specification from a GitHub issue?▼

Yes. The Skill accepts an optional GitHub issue link alongside your feature description, extracts relevant context, and uses it as input during the spec generation workflow to produce a standardized specification with related artifacts.

What's the best way to remove ambiguity from feature requests before implementation?▼

Ask clarifying questions during requirements capture to refine the feature intent. This Skill guides you through interactive refinement stages, eliminating vagueness and producing concrete acceptance criteria and testable specifications ready for development handoff.

How do I structure and export a feature specification to my repository?▼

Provide your feature description and work through the Skill's guided stages to generate a structured spec. The Skill writes the specification and related workflow artifacts directly to your repo, formatted for team review and integrated with git workflows.

Does this work with existing git repositories and jq for data processing?▼

Yes. The Skill depends on git and jq for repository integration and JSON processing. It reads from and writes to your existing repo structure, leveraging these tools to parse feature data and export standardized specifications.

What if my feature request is incomplete or lacks technical detail?▼

The Skill is designed for iterative refinement. It asks clarifying questions to extract missing details, progressively building context and specificity until ambiguity is resolved and acceptance criteria are concrete and testable.

Related Skills

Explore More Product & Management Skills→
B0yZ4kr14B0yZ4kr14

speckit-github-issues-import

Import a GitHub issue into a structured spec.md with requirements and acceptance criteria.

Community
Intermediate
chohra-medchohra-med
28

spec-harness-tickets

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

Community
Advanced
pegasus-isipegasus-isi

commit

Generate Conventional Commits from git status, diffs, and branch metadata.

Official
Intermediate
mkhsu2002mkhsu2002
1

doc-coauthoring

Guide structured co-authoring workflows for technical specs and proposals.

Community
Advanced