Convert feature ideas or issues into Ralph execution specs and GitHub issues.
npx skills add https://github.com/rjernst/dotfiles --skill create-spec-rjernst
Please help me install this Agent Skill. Skill: create-spec Source: https://github.com/rjernst/dotfiles/tree/main/claude/skills/create-spec Command: npx skills add https://github.com/rjernst/dotfiles --skill create-spec-rjernst
It turns a feature idea or an existing issue into a precise, self-contained execution spec that Ralph can run, reducing back-and-forth and missing requirements.
Use the create-spec skill by invoking /create-spec with your feature idea or an issue number, and it will generate a reviewable spec issue body ready for Ralph execution.
High-intent search queries and answers about installing and using this skill.
To generate an executable spec from a GitHub issue, you can use an automation tool to convert the issue into a self-contained, checkable execution spec with acceptance criteria and a templated task breakdown. This reduces missing requirements and back-and-forth during automated planning.
You can create a GitHub issue with a feature spec in your fork by using a CLI tool that resolves the repository via git remote get-url and executes gh issue create with an approved body file. This populates your fork with a labeled issue ready for automated execution.
Yes, you can search for existing issues using natural language to draft a feature spec. The planning agent detects natural-language input, searches issues in your fork, and bases the generated execution spec on the source issue's goal and context.
Yes, spec generation works with interactive workflows without prior code by conducting context-based interviews. It guides you through feature name, scope, constraints, and acceptance criteria to produce a reviewable spec issue body without writing code.
An executable feature spec for a planning agent includes a self-contained, checkable task breakdown with frontmatter branch, base, and depends fields as needed. It also contains acceptance criteria and constraints to ensure the automation loop can run.
Yes, you need a GitHub fork to create an executable spec issue because the tool resolves the target repository using git remote get-url and creates the labeled issue using gh issue create --repo origin-repo within that fork.
theZMCRead GitHub issue status, metadata, and comments via gh CLI.
wadvancedEnrich GitHub issues into implementation-ready specifications for Elixir/Phoenix/Ash codebases.
tiankong0101-byteEnforce a spec-first workflow with brainstorming, TDD, debugging, and branch completion.
fhltaConvert spec-kit task lists into dependency-ordered GitHub issues.
