القائمة
Synchronize specs/tasks.md with Plans.md. Expands spec tasks into Plans.md format with spec reference links, and reflects Plans.md completions back to tasks.md. Bridges SDD and Harness workflows.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create Conventional Commits with type prefix, breaking change detection, dry-run preview, and strict rules against ticket IDs in messages. **AUTOMATICALLY USE** when: (1) Creating git commits ("commit", "git commit") (2) Suggesting commit messages ("commit message") (3) Splitting commits ("split commits") (4) Fixing commit messages ("fix commit") (5) Any git commit related request
Orchestrate the full release process: push to develop, generate release summary, propose version bump, update package.json files, generate CHANGELOG, create release PR, and monitor CI. Supports dry-run preview mode. **AUTOMATICALLY USE** when: (1) Releasing a new version ("release", "cut a release", "prepare release") (2) Bumping version ("version bump", "bump version") (3) Creating release PRs ("release PR") (4) Generating changelogs ("changelog", "release notes") (5) Any release-related request
Record knowledge to the local knowledge base after solving problems, making design decisions, or discovering reusable patterns. Invoke whenever you have just fixed a bug, made an architectural choice, found a reusable pattern, learned something from external sources, or completed a refactoring. Capturing while context is fresh prevents knowledge loss across sessions.
Search the local knowledge base for past solutions, design decisions, and patterns before starting work. Invoke when facing an error or exception, when approaching an unfamiliar area of the codebase, or when considering implementation approaches. Prevents re-solving already-solved problems and surfaces relevant context proactively.
Get contextual knowledge suggestions based on the current work context — the file being edited, the task being performed, or the error being investigated. Invoke at the start of a work session, when opening a new file, or when beginning a feature. Surfaces relevant past knowledge proactively without requiring a specific query.
Analyze existing codebase to inform spec design. Scans specified packages or directories to extract architecture patterns, public APIs, dependency relationships, and test coverage. Output feeds directly into design.md.
| name | sdd-sync |
| description | Synchronize specs/tasks.md with Plans.md. Expands spec tasks into Plans.md format with spec reference links, and reflects Plans.md completions back to tasks.md. Bridges SDD and Harness workflows. |
Bridge the SDD workflow (specs/) with the Harness workflow (Plans.md). Ensures both systems stay in sync without manual duplication.
$ARGUMENTS (optional): Spec ID (e.g., KNOW-001). If omitted, sync all active specs.specs/KNOW-{NNN}-*/tasks.md### KNOW-001: Push-based capture
Spec: specs/KNOW-001-push-based-capture/
- [ ] Write tests for CaptureListener interface (see design.md §Architecture)
- [ ] Implement CaptureListener (see design.md §Interface Definitions)
- [ ] Write integration tests (see requirements.md AC-1 through AC-3)
specs/KNOW-{NNN}-*/tasks.mdCompare both directions and report discrepancies:
## Sync Report: KNOW-001
### Forward (tasks.md → Plans.md)
- 3 tasks added to Plans.md
- 0 tasks already present
### Reverse (Plans.md → tasks.md)
- 2 completions synced to tasks.md
- 0 drift detected
### Warnings
- (none)
docs/workflows/sdd-overview.md — How SDD and Harness relate