Menu
Use when you have a rough user story, bug report, or feature idea that needs to become a well-structured GitHub issue.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Stage B of /devflow-weekly: given the bundled context of every occurrence PR for one recurring pattern, re-derive the root cause, make the intervention edits in the working tree, and return the touched paths + PR title + PR body as JSON. Invoked as a subagent on a branch the orchestrator already created.
Run the weekly devflow self-improvement loop locally: scan freshly-merged watched-author PRs, write per-PR retrospective entries (LLM only for PRs that fail the mechanical clean-gate), derive recurring patterns, and open one human-reviewed intervention PR per actionable pattern. Use when running the weekly devflow retrospective + audit.
Use when setting up external documentation for the first time, performing a comprehensive documentation refresh, or when large portions of internal docs need corresponding external docs created.
Use when setting up internal documentation for the first time, when the docs directory is empty or poorly organized, or when a codebase has no structured developer documentation yet.
Use when a PR has customer-visible changes (new features, bug fixes, UI changes) that need a release note entry, or when finalizing a branch before merge.
Use when internal documentation has been updated and external customer-facing docs need to be aligned, or when checking for outdated, missing, or confidential content in external docs.
| name | create-issue |
| description | Use when you have a rough user story, bug report, or feature idea that needs to become a well-structured GitHub issue. |
| argument-hint | <user-story> |
If $ARGUMENTS is empty, ask the user to describe their user story, bug report, or feature idea before proceeding.
Invoke the /docs-verify skill with the topic extracted from the user story (e.g., /docs-verify survey module).
This will verify and update documentation in docs/internal/ for the relevant features.
After the skill completes, commit and push the documentation changes.
Evaluate whether the user story needs clarification based on the doc findings and the story itself.
General principle: Identify gaps, ambiguities, or risks that would produce a weak or incorrect GitHub issue. If the story is clear and the feature is straightforward, skip to Step 3.
Ask when:
Skip when:
If clarification is needed:
Record all Q&A pairs for the handoff:
## Clarifications
Q: [question asked]
A: [user's answer]
Use the devflow:github-issue-creator subagent to create a well-structured GitHub issue. Do not add labels to the created issue.
Pass to devflow:github-issue-creator:
User Story (rough draft): $ARGUMENTS