메뉴
Query specs via speq CLI. Search scenarios, list features, validate structure.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Audit a speq project's health — spec-library structure, feature/decision-log/plan validation, mission-to-spec sync, unrecorded plans, and gitignore hygiene — then guide fixes. Use when the user asks to audit, health-check, doctor, lint, or sanity-check the specs or repo, or after cloning or inheriting a speq project.
Code review tag taxonomy and findings output format — guardrail violations, dead code, obsolete tests, bad comments, optimizations, YAGNI/over-engineering. Triggered by code-reviewer.
Headless follow-up to speq-plan-pr. Continues on a plan's feat/plan-name branch, runs speq-implement, bumps the version, runs the real test suites, records only if green, then pushes and opens/updates a PR. Arg: plan name, PR number, or branch name.
Orchestrate implementation of reviewed plans according to the spec deltas. Arg: <plan-name>.
Create specs/mission.md via interactive interview. Detects brownfield vs greenfield.
Headless, non-interactive version of speq-plan. Plans a feature without a live interview, commits the result to a feat/plan-name branch, and opens a PR. If a decision genuinely needs a human, it persists the partial plan and open questions and asks in a PR comment instead of blocking. Arg — plan name, feature intent text, PR number, or branch name.
| name | speq-cli |
| description | Query specs via speq CLI. Search scenarios, list features, validate structure. |
Spec-driven development via the speq CLI. The spec CLI is installed locally and available in the path. Invoke via speq.
Never read full spec files without searching first.
Apply information foraging — search narrows the scent trail before committing context window budget.
| Command | Purpose |
|---|---|
speq domain list | List all domains |
speq feature list | Tree view of all features |
speq feature list <domain> | Features in a domain |
speq feature get <domain>/<feature> | Full feature spec |
speq feature get "<domain>/<feature>/<scenario>" | Single scenario |
speq search query "<query>" | Semantic search |
speq feature validate | Validate all specs |
speq feature validate <domain>/<feature> | Validate single feature |
1. Search first
speq search query "<relevant terms>"
2. Get specific content
speq feature get "<domain>/<feature>/<scenario>"
3. Validate after changes
speq feature validate
Finding error handling scenarios:
# Search for related scenarios
speq search query "error handling validation"
# Get specific scenario
speq feature get "cli/validate/Validation fails on missing field"
# Validate structure
speq feature validate cli/validate
# Wrong: Loading entire spec files
cat specs/cli/validate/spec.md
# Right: Search and get specific
speq search query "validation"
speq feature get "cli/validate/Required field missing"