메뉴
Fast spec creation with sensible defaults. No questions asked. Use when: quick spec, vibe spec, fast spec, baldrick vibe. Triggers on: vibe, quick spec, fast spec, no questions.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Execute Baldrick iterations on existing specs. Use when: run baldrick, execute specs, implement features, start working. Triggers on: baldrick run, run specs, implement, execute features.
Iteratively improve test coverage until target is reached. Use when: improve coverage, test coverage, coverage target, baldrick coverage. Triggers on: coverage, test coverage, coverage loop.
Iteratively reduce code entropy by fixing smells and improving quality. Use when: cleanup, code smells, entropy, refactor loop, baldrick entropy. Triggers on: entropy, cleanup, code smells, reduce entropy.
Iteratively fix all linting errors until clean. Use when: fix lint, lint errors, lint loop, baldrick lint-fix. Triggers on: lint, fix lint, lint errors, lint loop.
Generate PR documentation from completed spec and git diff. Use when: pr docs, generate docs, pull request docs, baldrick docs. Triggers on: pr docs, generate docs, document changes.
Create a feature specification for Baldrick. Use when: create a spec, new feature, write spec for, plan this feature. Triggers on: create spec, baldrick create, new spec, feature spec.
| name | spec-vibe |
| description | Fast spec creation with sensible defaults. No questions asked. Use when: quick spec, vibe spec, fast spec, baldrick vibe. Triggers on: vibe, quick spec, fast spec, no questions. |
Generate a feature specification immediately with sensible defaults. No clarifying questions.
Philosophy: Speed over perfection. Make reasonable assumptions and generate.
specs/[feature-name].mdCRITICAL: Do NOT ask questions. Just generate the spec immediately.
Required YAML Frontmatter:
---
id: feature-name-v1 # Unique identifier (kebab-case + version)
title: "Feature Title"
passes: false
priority: medium # high | medium | low
risk: standard # spike | integration | standard | polish
created: YYYY-MM-DD
depends_on: [] # Array of spec IDs this depends on (optional)
---
Required Sections:
When details are unclear, assume:
Each spec must be completable in ONE Baldrick iteration.
Right-sized:
Too big (split these):
---
id: task-priority-v1
title: "Add Task Priority"
passes: false
priority: medium
risk: standard
created: 2026-01-11
depends_on: []
---
# Add Task Priority
> **One-liner:** Allow users to set high/medium/low priority on tasks.
## Context
- **User**: Task owner
- **Trigger**: Creating or editing a task
- **Success**: Priority persists and displays correctly
## Scope
- **In**: Priority field, colored badge display
- **Out**: Priority-based notifications, auto-priority
## Examples
| Input | Expected |
|-------|----------|
| Set priority "high" | Red badge appears |
| Default | Gray badge (medium) |
## Scenarios
### Set priority on task
Given I am editing task "Review PR"
When I select "high" priority
Then the task is saved with priority "high"
And a red badge is displayed
### Invalid priority rejected
Given I am editing a task
When I submit with invalid priority "urgent"
Then I see error "Invalid priority"
## Done When
- [ ] Priority dropdown in task form
- [ ] Colored badge on task cards
- [ ] Build passes
- [ ] Tests pass
.md)specs/[feature-name].md (kebab-case, matches id without version)id field## Done When[placeholder])specs/[feature-name].md