メニュー
Update feature progress log and check off completed tasks. Use when user completes implementation tasks, makes commits, or indicates work is done. ASKS BEFORE MODIFYING files. Updates plan.md progress log section and implementation step checkboxes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use to create or update the per-author Ghost style guide from all available signals — interview answers, reference docs, and the published corpus — and to fold a newly approved post into it. Triggers on "build my style guide", "update the style guide", "learn my voice from my posts", and is invoked by push-draft after a successful push.
Use to write the first full draft of a Ghost blog post locally, matching the author's style guide, then self-audit it against the anti-pattern checklist. Triggers on "draft a post about X", "write the first draft", "start a new blog post".
Use to revise an existing local Ghost draft section by section with the author, improving formatting, voice, and accuracy. Triggers on "revise this post", "let's go through it section by section", "tighten this draft".
Use when first connecting a project to a Ghost site for the ghost plugin, or whenever Ghost credentials are missing/unverified — onboards the Ghost Admin API key, enables the plugin at project level, and verifies the connection. Triggers on "set up ghost", "connect my ghost site", "ghost credentials", "the ghost mcp isn't working".
Use to push a finished local Ghost draft to the Ghost site as a draft (never published) — pull-guards against in-editor edits, uploads the feature image, creates or updates the post, verifies links, and feeds the approved post back into the style guide. Triggers on "push this to ghost", "send the draft to ghost", "publish to ghost as a draft".
Use to write a Ghost blog post end to end, walking the full plan→draft→revise→push flow in one guided pass. Triggers on "write a post about X end to end", "take this from idea to a ghost draft", "guide me through writing a post".
| name | tracking-progress |
| description | Update feature progress log and check off completed tasks. Use when user completes implementation tasks, makes commits, or indicates work is done. ASKS BEFORE MODIFYING files. Updates plan.md progress log section and implementation step checkboxes. |
| allowed-tools | Read, Edit |
Track feature implementation progress by updating plan.md when tasks are completed.
Invoke this skill when the user:
tracking-progress works on active and paused features. It does NOT work on replaced or abandoned features — those are tombstones; no further progress should be tracked. If invoked on a tombstoned feature, refuse and tell the user to run /feature-state <id> active first if they want to resume work.
This skill modifies files. Always ask before making changes.
Read docs/features/DASHBOARD.md and look at the In Progress section to find current features.
If multiple exist, check context or ask which one.
Read docs/features/[id]/plan.md
Locate:
From the user's statement, identify what was completed and match it to implementation steps.
Prepare:
- [ ] → - [x]Show proposed changes, get confirmation, then use Edit tool to apply.
User: "Done with the JWT token refresh logic"
Response:
Update progress in plan.md?
1. Add progress log entry:
### 2026-01-15
- Completed JWT token refresh logic in auth/tokens.ts
- Next: Implement session timeout handling
2. Mark complete:
- [x] Implement JWT token refresh logic
Proceed? (yes/no)
After confirmation:
Progress updated in plan.md:
- Added log entry for 2026-01-15
- Marked complete: Implement JWT token refresh logic
Remaining steps: 4 of 7
This skill works with:
/feature-review-impl - Uses plan.md checkbox state to auto-generate PR body/feature-ship - Relies on accurate progress tracking