scaffold-issue

Scaffold a branch-specific specification from a GitHub issue.

11|2|Updated Sep 8, 2015
One-click install
npx skills add https://github.com/jitrapon/astro-mobile --skill scaffold-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scaffold-issue
Source: https://github.com/jitrapon/astro-mobile/tree/main/.claude/skills/scaffold-issue
Command: npx skills add https://github.com/jitrapon/astro-mobile --skill scaffold-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a GitHub issue into a structured, branch-scoped specification so planning starts from a clear, consistent brief instead of a blank document.

Core Features & Use Cases

  • Issue Distillation: Extracts the issue’s overview, objective, constraints, and references into concise SPEC sections.
  • Branch-Aware Workflow: Handles main-branch branch creation, feature-branch prompts, and safe local-only commits.
  • Spec-Driven Handoff: Prepares the specification for the next planning step without drifting into implementation details.
  • Use Case: When a product or engineering lead says to scaffold issue 123, this Skill produces the SPEC foundation and hands it off for planning.

Quick Start

Use the scaffold-issue skill to turn issue #123 into a populated .claude/SPEC.md, confirm or create the branch, and commit the scaffolded specification.

Frequently Asked Questions about scaffold-issue

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

FAQPage Schema
How do I generate a project specification from a GitHub issue?

To generate a project specification from a GitHub issue, the Skill retrieves the issue via GitHub CLI and distills its overview, objective, and references into a structured SPEC.md file. It operates branch-aware, handling main-branch creation and feature-branch prompts.

What is a spec-driven planning workflow for GitHub issues?

A spec-driven planning workflow for GitHub issues extracts issue details into a branch-scoped specification before coding begins. This approach ensures planning starts from a consistent brief rather than a blank document, separating spec creation from implementation.

Can I scaffold a spec from a closed GitHub issue on my current branch?

Yes, you can scaffold a spec from a closed GitHub issue on your current branch. The Skill supports closed-issue follow-ups directly from your existing repository branch, extracting the relevant context into a local specification file.

Do I need the GitHub CLI installed to create an issue spec?

Yes, the GitHub CLI is required to create an issue spec because the Skill relies on it for issue retrieval. It fetches issue data by number or URL to distill the content into structured specification sections.

How do I commit a scaffolded specification to a feature branch?

To commit a scaffolded specification to a feature branch, the Skill handles branch-aware confirmation and performs a safe local-only commit. It preserves original issue references within the committed SPEC.md file.

Best way to prepare a GitHub issue for development planning?

The best way to prepare a GitHub issue for development planning is to distill it into a code-agnostic specification. This Skill extracts the objective and constraints into SPEC sections, creating a clear handoff without drifting into implementation details.