spec-authoring

Generates specification drafts and analyzes PR review feedback using the Gemini CLI.

Updated Jul 13, 2024
One-click install
npx skills add https://github.com/Reading-Advantage-Thailand/codecamp-advantage --skill spec-authoring-reading-advantage-thailand
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-authoring
Source: https://github.com/Reading-Advantage-Thailand/codecamp-advantage/tree/main/.claude/skills/spec-authoring
Command: npx skills add https://github.com/Reading-Advantage-Thailand/codecamp-advantage --skill spec-authoring-reading-advantage-thailand

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Writing feature specifications from scratch and synthesizing scattered PR review comments into actionable changes is slow and error-prone. This Skill automates both steps of a spec-driven development workflow using AI-assisted drafting and feedback analysis. ## Core Features & Use Cases - Draft Proposal Generation: The propose command creates a new directory under docs/changes/ and generates three coherent files (proposal.md, spec-delta.md, tasks.yml) via chained Gemini CLI calls, where each document uses the previous one as context. - PR Feedback Synthesis: The update command fetches review comments from a GitHub PR using the gh CLI, combines them with the existing spec files, and asks Gemini to produce a per-file summary of recommended changes. - Use Case: A product manager wants to propose a real-time notifications feature. They run the propose command, review the generated proposal, spec delta, and task breakdown, open a Spec PR, and later use the update command to turn reviewer comments into a concrete revision plan. ## Quick Start Ask the assistant to create a spec proposal for your feature, for example: propose a change called "Real-time Notifications" using the spec-authoring workflow.

Frequently Asked Questions about spec-authoring

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

FAQPage Schema
How do I generate a feature specification draft with Gemini CLI?▼

Run bash scripts/spec-authoring.sh propose "Feature Name" from the repository root. The script creates a directory under docs/changes/ and generates proposal.md, spec-delta.md, and tasks.yml through chained Gemini calls that share context for coherence.

How do I analyze GitHub PR review comments automatically?▼

Run bash scripts/spec-authoring.sh update PR_NUMBER. The script uses the gh CLI to fetch the PR branch and all review comments, then sends them with your spec files to Gemini, which returns a per-file summary of recommended changes.

What tools are required for the spec-authoring workflow?▼

You need the gemini CLI installed and authenticated, the gh CLI authenticated to your GitHub repository, and a project initialized with docs/specs/ and docs/changes/ directories. The script is a Bash script, so a POSIX-compatible shell is required.

Why does the update command fail to find my proposal directory?▼

The update command derives the directory name from the PR branch name by stripping the spec/ prefix, then looks under docs/changes/. It fails if you are not on the correct branch or if the local directory name does not match the branch name.

What files does the propose command generate?▼

It generates three files: proposal.md with problem statement and success criteria, spec-delta.md with detailed requirements and design decisions, and tasks.yml with a labeled task breakdown including type, component, and priority fields.