القائمة
Creates a GitHub epic and child issues from a design document's implementation plan. Use when a design doc has a reviewed plan section ready to be converted into trackable work.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Automates the build and local installation of the Chronicles application on macOS. Use when the user wants to test a local build of the application by installing it into their /Applications folder.
Creates a tagged GitHub draft release with AI-generated summary, signed DMG artifact, and auto-generated changelog. Use when the user wants to cut a new release.
Creates a single GitHub issue with proper formatting, linked to a parent epic. Designed to be delegated to a sub-agent (Sonnet/Haiku).
Implements a GitHub issue using Sonnet in an isolated worktree, with Opus reviewing the result. Escalates to a WIP pull request when human judgment is needed.
Automates the build and local installation of the Chronicles application on macOS. Use when the user wants to test a local build of the application by installing it into their /Applications folder.
Reviews and validates the multi-platform skill structure (Claude, Gemini, Codex) in this repository. Use when adding or modifying skills to ensure they follow project conventions and are correctly proxied.
| name | design-to-issues |
| description | Creates a GitHub epic and child issues from a design document's implementation plan. Use when a design doc has a reviewed plan section ready to be converted into trackable work. |
Read a design document's implementation plan and produce a GitHub epic issue with linked child issues for each work item.
gh CLI authenticatedThis skill accepts one argument: the path to the design document (e.g. docs/designs/theming.md).
Read the design doc at the provided path. Identify:
Compose the epic issue body. Format:
## Overview
<1-2 sentence summary of the project from the design doc's executive summary>
## Design document
<Relative path to the design doc in the repo, as a link>
## Plan
<Numbered checklist of all work items from the plan, including deferred items marked as such>
- [ ] #XX — <Item 1 title>
- [ ] #XX — <Item 2 title>
- [ ] [DEFERRED] <Item N title>
## Notes
- Deferred items are tracked here for completeness but do not have child issues yet.
- Check off items as their child issues are closed.
The #XX placeholders are filled in after child issues are created (step 4).
gh issue create --title "<Project name>: implementation epic" --body "<body>"
Save the epic issue number.
For each non-deferred plan item, delegate to a sub-agent using the gh-create skill. Use the Agent tool with model: "haiku" and subagent_type: "general-purpose".
Provide each sub-agent with:
Run independent issue creations in parallel where possible (items without dependencies between them).
After all child issues are created, edit the epic body to replace #XX placeholders with actual issue numbers:
gh issue edit <epic-number> --body "<updated body with real issue numbers>"
Show the user: