Track Management
Unverified●29/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add track-managementWho is stuck, and on what
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
The whole source
Frontmatter — 3 properties
| name | track-management |
|---|---|
| description | Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations. |
| version | 1.0.0 |
| 1 | --- |
| 2 | name: track-management |
| 3 | description: Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations. |
| 4 | version: 1.0.0 |
| 5 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 6 | |
| 7 | # Track Management |
| 8 | |
| 9 | Guide for creating, managing, and completing Conductor tracks - the logical work units that organize features, bugs, and refactors through specification, planning, and implementation phases. |
| 10 | |
| 11 | ## When to Use This Skill |
| 12 | |
| 13 | - Creating new feature, bug, or refactor tracks |
| 14 | - Writing or reviewing spec.md files |
| 15 | - Creating or updating plan.md files |
| 16 | - Managing track lifecycle from creation to completion |
| 17 | - Understanding track status markers and conventions |
| 18 | - Working with the tracks.md registry |
| 19 | - Interpreting or updating track metadata |
| 20 | |
| 21 | ## Detailed patterns and worked examples |
| 22 | |
| 23 | Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient. |
| 24 | |
| 25 | ## Best Practices |
| 26 | |
| 27 | 1. **One track, one concern**: Keep tracks focused on a single logical change |
| 28 | 2. **Small phases**: Break work into phases of 3-5 tasks maximum |
| 29 | 3. **Verification after phases**: Always include verification tasks |
| 30 | 4. **Update markers immediately**: Mark task status as you work |
| 31 | 5. **Record SHAs**: Always note commit SHAs for completed tasks |
| 32 | 6. **Review specs before planning**: Ensure spec is complete before creating plan |
| 33 | 7. **Link dependencies**: Explicitly note track dependencies |
| 34 | 8. **Archive, don't delete**: Preserve completed tracks for reference |
| 35 | 9. **Size appropriately**: Keep tracks between 1-5 days of work |
| 36 | 10. **Clear acceptance criteria**: Every requirement must be testable |
| 37 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Task Coordination StrategiesDecompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.◐◐◐◐◐●35/40Ebay Seller Tools·····●34/40Tough Decision Advisor: Every Angle ConsideredHand in a decision you're stuck on. Get back a clear breakdown of every angle — the trade-offs, the risks, the blind spot, and a recommended path.●····●32/40DHDNA Profiler — Cognitive Pattern ExtractionPaste any email, proposal, or note someone wrote, and get back a plain-language read on how they think, what drives their decisions, and how they communicate.●····●32/40