Files
agents/conductor/templates/tracks.md
Seth Hobson f662524f9a feat: add Conductor plugin for Context-Driven Development
Add comprehensive Conductor plugin implementing Context-Driven Development
methodology with tracks, specs, and phased implementation plans.

Components:
- 5 commands: setup, new-track, implement, status, revert
- 1 agent: conductor-validator
- 3 skills: context-driven-development, track-management, workflow-patterns
- 18 templates for project artifacts

Documentation updates:
- README.md: Updated counts (68 plugins, 100 agents, 110 skills, 76 tools)
- docs/plugins.md: Added Conductor to Workflows section
- docs/agents.md: Added conductor-validator agent
- docs/agent-skills.md: Added Conductor skills section

Also includes Prettier formatting across all project files.
2026-01-15 17:38:21 -05:00

1.4 KiB

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}}/


[ ] {{TRACK_ID}}: {{TRACK_NAME}}

Description: {{TRACK_DESCRIPTION}} Priority: {{PRIORITY}} Folder: ./tracks/{{TRACK_ID}}/


Completed Tracks


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