القائمة
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.
التثبيت باستخدام 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 comprehensive spec with diagrams, flows, and thorough documentation. Use when: detailed spec, comprehensive spec, full spec, baldrick spec. Triggers on: detailed, comprehensive, full spec, thorough.
| name | spec-create |
| description | 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. |
Create detailed feature specifications for the Baldrick autonomous agent system.
Philosophy: Skills manufacture work items. Baldrick consumes them.
specs/[feature-name].mdImportant: Do NOT implement. Just create the spec.
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:
Ask with lettered options for quick responses:
1. What is the primary goal?
A. New user onboarding
B. Power user workflow
C. Admin management
D. Other: [specify]
2. What is the scope?
A. Minimal viable (just core)
B. Full-featured
C. Just backend/API
D. Just UI
User can respond with "1A, 2B" for speed.
Each spec must be completable in ONE Baldrick iteration (one context window).
Right-sized:
Too big (split these):
Rule of thumb: If you cannot describe the change in 2-3 sentences, it is too big.
Priority:
high - Core functionality, blocking other workmedium - Important but not blocking (default)low - Nice to have, polishRisk:
spike - Unknown territory, research neededintegration - Touches multiple systemsstandard - Normal feature work (default)polish - UI tweaks, cleanup---
id: task-priority-v1
title: "Add Priority Field to Tasks"
passes: false
priority: high
risk: standard
created: 2026-01-11
depends_on: []
---
# Add Priority Field to Tasks
## One-liner
Allow users to set high/medium/low priority on tasks.
## Context
- **User**: Task owner
- **Trigger**: Editing or creating a task
- **Success**: Priority persists and displays correctly
## Scope
- **In**: Priority field, colored badge display, filter by priority
- **Out**: Priority-based notifications, auto-priority based on due date
## Examples
| Input | Expected |
|-------|----------|
| Set priority to "high" | Red badge appears |
| Filter by "high" | Only high-priority tasks shown |
## Scenarios
### Set priority on new task
Given I am creating a new task
When I select "high" priority
Then the task is saved with priority "high"
And a red badge is displayed
### Filter by priority
Given I have tasks with mixed priorities
When I select "High" in the filter
Then only high-priority tasks are shown
## Done When
- [ ] Priority dropdown in task form
- [ ] Colored badge on task cards (red/yellow/gray)
- [ ] Filter dropdown works
- [ ] Build passes
- [ ] Tests pass
.md)specs/[feature-name].md (kebab-case, matches id without version)id field## Done Whenspecs/[feature-name].md