create-spec

Convert GitHub issues into persistent Working Documents with steering references.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/IKcoding-jp/Roast-Plus --skill create-spec-ikcoding-jp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-spec
Source: https://github.com/IKcoding-jp/Roast-Plus/tree/main/.claude/skills/create-spec
Command: npx skills add https://github.com/IKcoding-jp/Roast-Plus --skill create-spec-ikcoding-jp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of persistent Working Documents from GitHub issues when the standard /issue-creator flow isn't used, capturing context for future reference.

Core Features & Use Cases

  • Persistent design notes: Stores issue context as Working Documents for cross-session reuse.
  • Steering integration: Reads steering docs to align with project standards during generation.
  • One-time confirmation: Allows user to review and approve generated Working Documents before saving.

Quick Start

Run the skill with an Issue number to generate the corresponding Working Documents for review.

Frequently Asked Questions about create-spec

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

FAQPage Schema
How do I convert GitHub issues into persistent working documents?

To convert GitHub issues into persistent working documents, this Skill extracts issue context and generates durable design notes for cross-session reuse. It reads steering docs to align with project standards during generation.

How do I preserve context and decisions from GitHub issues across sessions?

Preserving context and decisions from GitHub issues requires storing them as persistent working documents. This Skill captures the issue context and traces decisions, ensuring details remain accessible for future reference.

Can I review and approve generated working documents before saving them?

Yes, you can review and approve generated working documents before saving. The workflow includes a one-time confirmation step that allows you to check the extracted issue context before it is permanently stored.

Do I need steering documents to generate working documents from issues?

Steering documents are read during generation to align outputs with project standards. While the workflow applies when issues require manual specification, having steering docs ensures the generated working documents match conventions.

When should I use manual specification to generate working documents instead of standard flows?

Manual specification to generate working documents is needed when the standard issue-creator flow is not used. This approach captures context from external sources, ensuring traceability across sessions where standard automation falls short.