Files
agents/plugins/conductor/templates/tracks.md
Seth Hobson 1408671cb7 fix(conductor): move plugin to plugins/ directory for proper discovery
Conductor plugin was at root level instead of plugins/ directory,
causing slash commands to not be recognized by Claude Code.
2026-01-15 20:34:57 -05:00

54 lines
1.4 KiB
Markdown

# Track Registry
This file maintains the registry of all development tracks for the project. Each track represents a distinct body of work with its own spec and implementation plan.
## Status Legend
| Symbol | Status | Description |
| ------ | ----------- | ------------------------- |
| `[ ]` | Pending | Not yet started |
| `[~]` | In Progress | Currently being worked on |
| `[x]` | Completed | Finished and verified |
## Active Tracks
### [ ] {{TRACK_ID}}: {{TRACK_NAME}}
**Description:** {{TRACK_DESCRIPTION}}
**Priority:** {{PRIORITY}}
**Folder:** [./tracks/{{TRACK_ID}}/](./tracks/{{TRACK_ID}}/)
---
### [ ] {{TRACK_ID}}: {{TRACK_NAME}}
**Description:** {{TRACK_DESCRIPTION}}
**Priority:** {{PRIORITY}}
**Folder:** [./tracks/{{TRACK_ID}}/](./tracks/{{TRACK_ID}}/)
---
## Completed Tracks
<!-- Move completed tracks here -->
---
## Track Creation Checklist
When creating a new track:
1. [ ] Add entry to this registry
2. [ ] Create track folder: `./tracks/{{track-id}}/`
3. [ ] Create spec.md from template
4. [ ] Create plan.md from template
5. [ ] Create metadata.json from template
6. [ ] Update index.md with new track reference
## Notes
- Track IDs should be lowercase with hyphens (e.g., `user-auth`, `api-v2`)
- Keep descriptions concise (one line)
- Prioritize tracks as: critical, high, medium, low
- Archive completed tracks quarterly