43 lines
1.6 KiB
Markdown
43 lines
1.6 KiB
Markdown
---
|
|
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.
|
|
risk: safe
|
|
source: community
|
|
date_added: '2026-02-27'
|
|
---
|
|
|
|
# Track Management
|
|
|
|
Guide for creating, managing, and completing Conductor tracks - the logical work units that organize features, bugs, and refactors through specification, planning, and implementation phases.
|
|
|
|
## Use this skill when
|
|
|
|
- Creating new feature, bug, or refactor tracks
|
|
- Writing or reviewing spec.md files
|
|
- Creating or updating plan.md files
|
|
- Managing track lifecycle from creation to completion
|
|
- Understanding track status markers and conventions
|
|
- Working with the tracks.md registry
|
|
- Interpreting or updating track metadata
|
|
|
|
## Do not use this skill when
|
|
|
|
- The task is unrelated to track management
|
|
- You need a different domain or tool outside this scope
|
|
|
|
## Instructions
|
|
|
|
- Clarify goals, constraints, and required inputs.
|
|
- Apply relevant best practices and validate outcomes.
|
|
- Provide actionable steps and verification.
|
|
- If detailed examples are required, open `resources/implementation-playbook.md`.
|
|
|
|
## Resources
|
|
|
|
- `resources/implementation-playbook.md` for detailed patterns and examples.
|
|
|
|
## Limitations
|
|
- Use this skill only when the task clearly matches the scope described above.
|
|
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
|
|
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
|