메뉴
Search and filter features by state, assignee, priority, epic, dependency, type, or category. Use when the user wants to find features matching criteria — "what's paused", "what's court working on", "what's in the auth-overhaul epic", "what depends on X".
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-search |
| description | Search and filter features by state, assignee, priority, epic, dependency, type, or category. Use when the user wants to find features matching criteria — "what's paused", "what's court working on", "what's in the auth-overhaul epic", "what depends on X". |
| user-invocable | true |
| allowed-tools | Bash, Read |
You are executing the SEARCH FEATURES workflow — querying the backlog by filters and presenting a table.
$ARGUMENTS is a series of flags. Pass them through to the search script.
Supported filters:
--state <active|paused|replaced|abandoned>--assignee <name>--priority <P0|P1|P2>--type <Feature|Enhancement|Bug Fix|Tech Debt|Epic>--category <name>--epic <id> (children of an epic)--depends-on <id> (features that depend on the given ID)--archive (include replaced + abandoned)--format text|json (default text)If no filters: show all active features (excludes archive by default).
python3 ${CLAUDE_PLUGIN_ROOT}/skills/feature-search/scripts/search.py <project-root> $ARGUMENTS
Capture stdout.
For text output, render the markdown table as-is, plus a one-line summary above:
"N matching features:"
For JSON output (passed --format json), echo the JSON.
If results contain features in specific states, suggest:
/feature-state <id> active to resume/feature-plan <id> or /feature-autopilot <id>/feature-implement <id>If zero results:
--archive to include tombstones./feature-capture to add it.| User request | Command |
|---|---|
| "what's paused?" | /feature-search --state paused |
| "what is court working on?" | /feature-search --assignee court |
| "show all P0s" | /feature-search --priority P0 |
| "what's in the auth-overhaul epic?" | /feature-search --epic auth-overhaul |
| "what depends on user-roles?" | /feature-search --depends-on user-roles |
| "show abandoned features" | /feature-search --state abandoned --archive |