skills.rest
JamSuite
JamSuiteOFFICIAL
Explore all skills by this author →
GitHub

spec

Guide collaborative interviews to create structured spec documents.

1|1|Updated Feb 25, 2025
Search Tags:#planning#collaboration#spec#user-stories#acceptance-criteria#spec-management
One-click install
npx skills add https://github.com/JamSuite/jim --skill spec-jamsuite
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/JamSuite/jim/tree/main/skills/spec
Command: npx skills add https://github.com/JamSuite/jim --skill spec-jamsuite

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Create or update a feature, bug, or refactor spec through collaborative interview, turning rough ideas into a formal specification ready for planning and handoff.

Core Features & Use Cases

  • Guided interview process to extract problem statements, user stories, acceptance criteria, and scope.
  • Generates a structured spec document at docs/specs/{group}/{00X}-{name}/spec.md with type-specific sections and templates.
  • Integrates with jim's planning workflow, enabling seamless updates and reviews across product, design, and engineering.

Quick Start

Initiate a collaborative interview to transform a rough idea into a formal spec draft.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I turn rough ideas into structured specs with user stories and acceptance criteria?▼

A spec generated through collaborative interview produces a structured document at docs/specs/{group}/{00X}-{name}/spec.md. It includes type-specific sections for problem statements, user stories, acceptance criteria, and scope based on the provided template.

How do I write a spec for different types like features, bugs, or refactors?▼

The collaborative interview supports identifying whether your spec is a feature, bug, or refactor. It then collects the required problem statements, user stories, acceptance criteria, and scope to populate the correct template sections for your specific spec type.

Can I use collaborative spec management to integrate with my product planning workflow?▼

Specs created through the collaborative interview integrate directly into Jim's planning workflow. This enables seamless updates and reviews across product, design, and engineering teams once the formal specification document is generated and finalized.

What is the best way to define scope and acceptance criteria for a new feature?▼

Defining scope and acceptance criteria is handled by a guided interview that extracts these elements from your rough ideas. This ensures all necessary constraints and user stories are systematically captured into a structured spec template for formal review.

Do I need a specific template format to generate a spec document?▼

The generated spec document must follow the template defined in assets/spec-template.md. The collaborative interview process ensures all collected problem statements, user stories, and acceptance criteria map directly to this required template format.

Related Skills

Explore More Product & Management Skills→
ichabodcoleichabodcole

Idea to Spec

Transform rough app ideas into technology-agnostic specification documents.

Community
Advanced
LucasMalessaLucasMalessa

ring:using-pm-team

Orchestrate gate-based pre-development workflows and generate planning artifacts.

Community
Advanced
Andy-HNUAndy-HNU

cross-functional-collaboration

Coordinate collaboration across product, design, and engineering teams.

Community
Advanced
ChazzCoinChazzCoin

user-story

Convert rough descriptions into spec-task user stories with acceptance criteria.

Community
Intermediate