skills.rest
pamelia
pameliaCOMMUNITY
Explore all skills by this author →
GitHub

issue-to-spec

Transform GitHub issues into formal specification documents with acceptance criteria.

Updated Mar 22, 2026
Search Tags:#workflow#specification#interview#issue#product-management#docs-specs
One-click install
npx skills add https://github.com/pamelia/opencode-plugins --skill issue-to-spec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-to-spec
Source: https://github.com/pamelia/opencode-plugins/tree/main/skills/issue-to-spec
Command: npx skills add https://github.com/pamelia/opencode-plugins --skill issue-to-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Issue-to-Spec workflow orchestrates turning a GitHub issue into a complete, speakable spec by exploring the issue, interviewing the user, drafting a formal spec, and synchronizing with review steps.

Core Features & Use Cases

  • End-to-end issue-to-spec workflow: issue exploration, user interviews, formal spec authoring, complexity assessment, and optional spec hardening via /spec-review.
  • Collaboration: guides structured interviews and records decisions for traceability.
  • Output: a ready-to-publish specification document in docs/specs with clear acceptance criteria and rollout plan.

Quick Start

Provide a GitHub issue reference (e.g., #42) to start the end-to-end spec workflow.

Frequently Asked Questions about issue-to-spec

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

FAQPage Schema
How do I convert a GitHub issue into a formal specification document?▼

You can transform a GitHub issue into a formal specification by providing the issue reference to trigger an automated workflow that explores the issue, conducts user interviews, and drafts a production-ready spec document.

What is the process for turning development issues into production-ready specs?▼

The process uses stepwise refinement to explore the issue, interview the user, draft the formal spec, assess complexity, and optionally initiate a spec-review cycle, ensuring cross-functional stakeholders align around a testable spec.

How do I start the issue-to-spec workflow using a GitHub issue reference?▼

You start the workflow by providing a GitHub issue reference like #42 to initiate the end-to-end process, which includes issue exploration, user interviews, formal spec authoring, complexity assessment, and optional spec hardening.

Does the specification workflow support cross-functional team collaboration?▼

Yes, the workflow supports cross-functional teams by guiding structured interviews and recording decisions for traceability, ensuring all stakeholders align around a single, testable specification with clear acceptance criteria.

What output format does the specification generation process produce?▼

The process outputs a ready-to-publish specification document in the docs/specs directory, complete with clear acceptance criteria and a rollout plan for production readiness.

Can I initiate a spec-review cycle after drafting the specification?▼

Yes, you can optionally initiate a spec-review cycle after drafting the formal specification to harden the document and ensure it meets production-ready standards through synchronized review steps.

Related Skills

Explore More Product & Management Skills→
Lev-itLev-it

qa

Create GitHub issues from conversational bug reports with codebase context.

Official
Intermediate
lv416elv416e
6

test-driven-development

Write failing tests before production code using a red-green-refactor workflow.

Community
Intermediate
rickardprickardp
2

blueprint:status

Summarize Blueprint project governance by parsing ADR statuses and counting specs and patterns.

Community
Intermediate
cuongtl1992cuongtl1992
10

spec-writer

Generate structured PRDs with Problem Statement, User Stories, MoSCoW, and Success Metrics.

Community
Advanced