메뉴
Display project status and backlog overview. Use when user asks about current status, what's in progress, what to work on next, or wants a summary of the backlog. Read-only skill that formats DASHBOARD.md into a clear dashboard view.
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 | feature-status |
| description | Display project status and backlog overview. Use when user asks about current status, what's in progress, what to work on next, or wants a summary of the backlog. Read-only skill that formats DASHBOARD.md into a clear dashboard view. |
| allowed-tools | Read, Bash |
| user-invocable | true |
Provide a quick overview of project status and backlog.
Invoke this skill when the user asks:
$ARGUMENTS can be:
cat:<category> — filter all tables to that category (case-insensitive)state:<state> — filter to features with that state (e.g., state:paused)assignee:<name> — filter to features owned by that name--archive — include replaced and abandoned featuresFilters can stack: state:active assignee:court shows court's active features.
For filter combinations beyond what the dashboard table supports, fall back to invoking /feature-search with equivalent flags.
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."
Parse $ARGUMENTS for filter tokens before rendering:
cat:<value> — keep only rows whose Category column matches (case-insensitive). Display header: "Filtered by category: [value]"state:<value> — keep only rows whose State/Status column matches (case-insensitive). Display header: "Filtered by state: [value]"assignee:<value> — keep only rows whose Assignee column matches (case-insensitive). Display header: "Filtered by assignee: [value]"--archive — include the Archive section (replaced/abandoned features) in the output; omit it by defaultThe DASHBOARD.md may contain the following sections (render each that is present):
--archive flag is present)Display a scannable summary with:
Use tables for lists. Highlight P0 items.
For additional context on any feature, read its files:
docs/features/[id]/
├── idea.md # Full problem statement
├── plan.md # Implementation details (if in-progress)
└── shipped.md # Completion notes (if completed)
User: "What's the status?"
Response:
# Project Status
**Summary**: 1 in progress, 1 paused, 4 in backlog, 3 completed
## In Progress
- **Dark Mode Toggle** (P1) - Started 2024-01-18
## Paused
- **Offline Mode** (P2) - Paused 2024-01-12 (blocked: waiting on design)
## Backlog (Ready to Start)
| Priority | Name | Effort |
|----------|------|--------|
| P0 | User Authentication | Medium |
| P1 | API Rate Limiting | Small |
## Recently Completed
- Export Feature (2024-01-15)
- Search Improvements (2024-01-10)
This skill works with:
checking-backlog skill - For deeper dives into specific items/feature-plan - Suggest for starting backlog items/feature-implement - Suggest for writing code for in-progress items/feature-review-plan - Suggest for submitting plan for external review/feature-review-impl - Suggest for submitting implementation for external review/feature-ship - Suggest for merging the PR after external reviews pass