skills.rest
PVMalove
PVMaloveCOMMUNITY
Explore all skills by this author →
GitHub

to-spec

Synthesizes conversation context into a specification and publishes it as a GitHub epic issue.

Updated Aug 19, 2026
Search Tags:#specification#feature planning#github issues#gh cli#epic#triage labels#integration branch
One-click install
npx skills add https://github.com/PVMalove/claude-agent-harness --skill to-spec-pvmalove
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-spec
Source: https://github.com/PVMalove/claude-agent-harness/tree/main/skills/first-party/pvmalove/to-spec
Command: npx skills add https://github.com/PVMalove/claude-agent-harness --skill to-spec-pvmalove

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a long discovery conversation, teams lose context when manually writing specs and creating tracker issues. This Skill converts the existing conversation into a structured specification and publishes it directly to the GitHub issue tracker as an epic, without re-interviewing the user. ## Core Features & Use Cases - Two-Phase Workflow: First proposes test seams and an integration branch name for user approval, then drafts and publishes the spec only after confirmation. - Structured Spec Template: Generates a complete spec with problem statement, user stories, implementation decisions, testing decisions, out-of-scope boundaries, and discovery context file lists. - Tracker Integration: Publishes the spec via gh issue create --body-file, applies triage labels (bug/enhancement, workflow::specs, task-report::required), and creates the integration/<service-or-team> branch from the configured base branch. - Use Case: After a /grill-with-docs session clarifies a feature, run this Skill to produce the epic issue and its integration branch so /to-tickets can decompose it into sub-tasks. ## Quick Start Ask the agent to turn the current conversation into a spec and publish it to the issue tracker, then approve the proposed test seams and integration branch name when prompted.

Frequently Asked Questions about to-spec

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

FAQPage Schema
How do I turn a conversation into a spec and GitHub issue?▼

Run the to-spec skill after a discovery conversation. It proposes test seams and an integration branch for your approval, then drafts the spec from the template and publishes it with gh issue create --body-file, applying the appropriate triage labels.

How to create a GitHub issue from a markdown file with gh CLI?▼

Use gh issue create --body-file <path> instead of an inline --body heredoc. Spec bodies contain nested quotes and backticks that break heredoc quoting, so the file-based flag is required for reliable publication.

Does to-spec interview the user before writing the spec?▼

No. The skill explicitly forbids re-interviewing; it synthesizes only known facts and explicit assumptions from the prior conversation. If information is missing, the earlier grilling phase was incomplete.

What labels does the published epic issue get?▼

The epic receives bug or enhancement, workflow::specs (never workflow::ready, which requires decomposition first), and task-report::required unless told to skip. Ad-hoc epic::<slug> labels are not created; /to-tickets links sub-tasks natively as GitHub sub-issues.

What happens if the integration branch already exists?▼

The existing local or remote integration branch is reused without resetting, force-updating, or deleting it. If issue publication succeeds but branch creation fails, the skill reports the partial state and the exact recovery action instead of recreating the epic.

Related Skills

Explore More Software Engineering Skills→
islamu-ngoislamu-ngo
7

grill-me

Interviews users one question at a time to stress-test plans and high-criticality requirements.

Official
Intermediate
Benmore-StudioBenmore-Studio
1

github-issue-gen

Generate GitHub issues and epics from project requirements.

Official
Advanced
haryelramalhoharyelramalho

domain-modeling

Creates CONTEXT.md glossaries and ADR files documenting architectural decisions and vocabulary per bounded context.

Community
Advanced
MichaelSolatiMichaelSolati

to-prd

Synthesize conversation and codebase context into structured PRDs and publish them to the issue tracker.

Community
Intermediate