119 lines
2.8 KiB
Markdown
119 lines
2.8 KiB
Markdown
---
|
|
description: Create a new conductor track with spec, plan, and metadata
|
|
agent: tier1-orchestrator
|
|
subtask: true
|
|
---
|
|
|
|
# /conductor-new-track
|
|
|
|
Create a new conductor track following the Surgical Methodology.
|
|
|
|
## Arguments
|
|
$ARGUMENTS - Track name and brief description
|
|
|
|
## Protocol
|
|
|
|
1. **Audit Before Specifying (MANDATORY):**
|
|
Before writing any spec, research the existing codebase:
|
|
- Use `py_get_code_outline` on relevant files
|
|
- Use `py_get_definition` on target classes
|
|
- Use `grep` to find related patterns
|
|
- Use `get_git_diff` to understand recent changes
|
|
|
|
Document findings in a "Current State Audit" section.
|
|
|
|
2. **Generate Track ID:**
|
|
Format: `{name}_{YYYYMMDD}`
|
|
Example: `async_tool_execution_20260303`
|
|
|
|
3. **Create Track Directory:**
|
|
`conductor/tracks/{track_id}/`
|
|
|
|
4. **Create spec.md:**
|
|
```markdown
|
|
# Track Specification: {Title}
|
|
|
|
## Overview
|
|
[One-paragraph description]
|
|
|
|
## Current State Audit (as of {commit_sha})
|
|
### Already Implemented (DO NOT re-implement)
|
|
- [Existing feature with file:line reference]
|
|
|
|
### Gaps to Fill (This Track's Scope)
|
|
- [What's missing that this track will address]
|
|
|
|
## Goals
|
|
- [Specific, measurable goals]
|
|
|
|
## Functional Requirements
|
|
- [Detailed requirements]
|
|
|
|
## Non-Functional Requirements
|
|
- [Performance, security, etc.]
|
|
|
|
## Architecture Reference
|
|
- docs/guide_architecture.md#section
|
|
- docs/guide_tools.md#section
|
|
|
|
## Out of Scope
|
|
- [What this track will NOT do]
|
|
```
|
|
|
|
5. **Create plan.md:**
|
|
```markdown
|
|
# Implementation Plan: {Title}
|
|
|
|
## Phase 1: {Name}
|
|
Focus: {One-sentence scope}
|
|
|
|
- [ ] Task 1.1: {Surgical description with file:line refs}
|
|
- [ ] Task 1.2: ...
|
|
- [ ] Task 1.N: Write tests for Phase 1 changes
|
|
- [ ] Task 1.X: Conductor - User Manual Verification
|
|
|
|
## Phase 2: {Name}
|
|
...
|
|
```
|
|
|
|
6. **Create metadata.json:**
|
|
```json
|
|
{
|
|
"id": "{track_id}",
|
|
"title": "{title}",
|
|
"type": "feature|fix|refactor|docs",
|
|
"status": "planned",
|
|
"priority": "high|medium|low",
|
|
"created": "{YYYY-MM-DD}",
|
|
"depends_on": [],
|
|
"blocks": []
|
|
}
|
|
```
|
|
|
|
7. **Update tracks.md:**
|
|
Add entry to `conductor/tracks.md` registry.
|
|
|
|
8. **Report:**
|
|
```
|
|
## Track Created
|
|
|
|
**ID:** {track_id}
|
|
**Location:** conductor/tracks/{track_id}/
|
|
**Files Created:**
|
|
- spec.md
|
|
- plan.md
|
|
- metadata.json
|
|
|
|
**Next Steps:**
|
|
1. Review spec.md for completeness
|
|
2. Run `/conductor-implement` to begin execution
|
|
```
|
|
|
|
## Surgical Methodology Checklist
|
|
- [ ] Audited existing code before writing spec
|
|
- [ ] Documented existing implementations with file:line refs
|
|
- [ ] Framed requirements as gaps, not features
|
|
- [ ] Tasks are worker-ready (WHERE/WHAT/HOW/SAFETY)
|
|
- [ ] Referenced architecture docs
|
|
- [ ] Mapped dependencies in metadata
|