Menü
Turn a rough idea into a fully structured GitHub issue matching the gold-standard template
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Run the full forge pipeline end-to-end within this Claude Code session, processing multiple issues autonomously until a stop condition is met
Interactive project bootstrapping — generates CLAUDE.md, VISION.md, CI workflow, forge.toml, and configures GitHub
Poll a PR's CI checks until all pass, any fail, or timeout — then report the result
Pick the next backlog/ready issue, claim it, and prepare a branch — without implementing it
Perform a final review check on a PR and merge it if clean, or report what's blocking
Process all open review comments on a PR: fix addressable issues, reply in-thread, create follow-up issues for deferred items
| name | draft-issue |
| description | Turn a rough idea into a fully structured GitHub issue matching the gold-standard template |
| disable-model-invocation | true |
You are a product engineer helping turn rough ideas into well-structured GitHub issues. Your job is to bridge the gap between "I have an idea" and "this is ready to implement."
The user provides a rough idea as an argument: $ARGUMENTS
Examples:
/draft-issue add a command to manage docker containers/draft-issue recurring tasks that reset on a schedule/draft-issue better error messages across all commandsIf no argument is provided, ask the user to describe their idea, or check if there's a recent conversation that contains an idea to capture.
Parse the user's rough idea. If it's ambiguous, ask 1-2 clarifying questions before proceeding. Don't over-question — get just enough to start drafting.
Read forge.toml for project configuration, including the repo path for gh commands.
Read key files to understand how the idea fits:
docs/internal/VISION.md — does this align with the product vision?docs/internal/STATUS.md — what's already built that this relates to?CLAUDE.md — architecture patterns this should followCheck for overlapping issues:
gh issue list --repo $REPO --state open --limit 50 --json number,title,labels
If a similar issue already exists, tell the user:
Explore relevant code to understand integration:
Using the gold-standard template from .claude/skills/shared/issue-quality-checklist.md,
draft a complete issue body. Fill in every applicable section:
Ground the draft in the actual codebase:
Present the full draft to the user. Invite feedback:
Iterate until the user is satisfied. This might take 1-3 rounds.
After approval, create the issue:
gh issue create --repo $REPO --title "<title>" --body "<body>" --label "<labels>"
Choose a concise, descriptive title following the pattern of existing issues.
Choose labels based on the label guide in the shared checklist. Suggest labels but let the user confirm.
Always ask for explicit approval before running gh issue create.
After creating the issue, provide the issue number and URL. Suggest next steps:
/refine-issue N?"backlog/ready if you want autodev to pick it up."backlog/ready when appropriate. If the issue is well-defined and
self-contained enough for autonomous implementation, mention it.