菜单
Check project backlog when discussing feature ideas or priorities. Use when user mentions adding features, asks what's planned, discusses priorities, or proposes new functionality. Silently reads DASHBOARD.md to show relevant items and suggest /feature-capture for untracked ideas.
用 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 | checking-backlog |
| description | Check project backlog when discussing feature ideas or priorities. Use when user mentions adding features, asks what's planned, discusses priorities, or proposes new functionality. Silently reads DASHBOARD.md to show relevant items and suggest /feature-capture for untracked ideas. |
| allowed-tools | Read, Glob, Bash |
Automatically check the project backlog when the user discusses feature ideas, priorities, or planned work.
Invoke this skill when the user:
Scan the feature directories to generate a live dashboard:
python3 ${CLAUDE_PLUGIN_ROOT}/skills/shared/lib/run_dashboard.py <project_root> --stdout
If the script fails or docs/features/ doesn't exist: "No backlog found. Use /feature-capture to start tracking."
When checking for an existing feature, the dashboard's Archive section (collapsed <details>) contains replaced and abandoned features. By default, do not suggest these in match results — the user is looking for things they can work on. Exception: if the user's prompt explicitly mentions a tombstoned ID by name, surface it with a note like "This was replaced by X" so they know its history.
Parse the DASHBOARD.md tables to find:
For deeper context on a specific feature, read its files:
docs/features/[id]/
├── idea.md # Problem statement, priority, effort, impact
├── plan.md # Implementation details (if in-progress)
└── shipped.md # Completion notes (if completed)
Search idea.md for:
name in frontmatter (partial match, case-insensitive)affectedAreas (if user mentions specific areas)/feature-plan [id] if in backlog./feature-capture to add it.User: "We should add dark mode support"
Response:
This feature is already tracked:
**Dark Mode Toggle** (ID: dark-mode-toggle)
- Status: backlog
- Priority: P1
Ready to start! Use `/feature-plan dark-mode-toggle`
This skill works with:
/feature-capture - Suggest when idea isn't tracked/feature-plan - Suggest when item is in backlog/feature-status - For broader status queries