plan
Turn a sufficiently understood task into an ordered implementation plan with dependencies and verification. Orchestrate GhostyCode’s native plan state; do not build a parallel planner.
- License 许可
- MIT
- 最近更新
- 2026-11-01
- Stars
- ★ 8
- Forks
- 0
01 前言 Front Matter
- name
- plan
- invocation
- model+user
- description
- Turn a sufficiently understood task into an ordered implementation plan with dependencies and verification. Orchestrate GhostyCode’s native plan state; do not build a parallel planner.
03 SKILL.md 正文
Plan
When to use
Use when the task is understood well enough to sequence work, but not yet a single obvious next edit.
Non-goals
- Do not plan while key goals are still unknown — use interview first.
- Do not create a second planner outside GhostyCode plan/Work state.
Workflow
- Restate the goal and constraints.
- List ordered steps with dependencies.
- Mark verification for each risky step.
- Write the plan into GhostyCode’s native plan/Work surface.
- Wait for authorization before broad implementation.
Output shape
- Goal
- Steps (ordered)
- Verification
- Risks / open questions
04 同仓库更多 Skills
gh-treasure-hunt
Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.
gh-find-prs
Survey open GhostyCode PRs and triage each for mergeability and disposition against the real landing branch.
gh-file-issue
Use when filing a new GhostyCode GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-credit-harvest
Harvest one community PR into a release branch with authorship and credit preserved, verified green, and a warm thank-you.
gh-compile-issues
Triage N GitHub issues into a coverage matrix: fetch each, check current code, classify already-done/quick-fix/design/defer with cited evidence.
gh-close-issues
Close resolved GhostyCode issues only after verifying the landed commit/behavior, with a positive crediting comment; never from title alone.