track-management

Name: track-management
Author: wshobson

7.9kinstalls4.1kforks

How to install track-management?

wshobson/agents/track-management

$npx -y skills add wshobson/agents --skill track-management

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	# Track Management
2
3	Guide for creating, managing, and completing Conductor tracks - the logical work units that organize features, bugs, and refactors through specification, planning, and implementation phases.
4
5	## When to Use This Skill
6
7	- Creating new feature, bug, or refactor tracks
8	- Writing or reviewing spec.md files
9	- Creating or updating plan.md files
10	- Managing track lifecycle from creation to completion
11	- Understanding track status markers and conventions
12	- Working with the tracks.md registry
13	- Interpreting or updating track metadata
14
15	## Detailed patterns and worked examples
16
17	Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.
18
19	## Best Practices
20
21	1. One track, one concern: Keep tracks focused on a single logical change
22	2. Small phases: Break work into phases of 3-5 tasks maximum
23	3. Verification after phases: Always include verification tasks
24	4. Update markers immediately: Mark task status as you work
25	5. Record SHAs: Always note commit SHAs for completed tasks
26	6. Review specs before planning: Ensure spec is complete before creating plan
27	7. Link dependencies: Explicitly note track dependencies
28	8. Archive, don't delete: Preserve completed tracks for reference
29	9. Size appropriately: Keep tracks between 1-5 days of work
30	10. Clear acceptance criteria: Every requirement must be testable

People who liked this also viewed

6 picks

Type

track-management

7.9kinstalls4.1kforks

View on GitHub

How to install track-management?

wshobson/agents/track-management

$npx -y skills add wshobson/agents --skill track-management

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	# Track Management
2
3	Guide for creating, managing, and completing Conductor tracks - the logical work units that organize features, bugs, and refactors through specification, planning, and implementation phases.
4
5	## When to Use This Skill
6
7	- Creating new feature, bug, or refactor tracks
8	- Writing or reviewing spec.md files
9	- Creating or updating plan.md files
10	- Managing track lifecycle from creation to completion
11	- Understanding track status markers and conventions
12	- Working with the tracks.md registry
13	- Interpreting or updating track metadata
14
15	## Detailed patterns and worked examples
16
17	Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.
18
19	## Best Practices
20
21	1. One track, one concern: Keep tracks focused on a single logical change
22	2. Small phases: Break work into phases of 3-5 tasks maximum
23	3. Verification after phases: Always include verification tasks
24	4. Update markers immediately: Mark task status as you work
25	5. Record SHAs: Always note commit SHAs for completed tasks
26	6. Review specs before planning: Ensure spec is complete before creating plan
27	7. Link dependencies: Explicitly note track dependencies
28	8. Archive, don't delete: Preserve completed tracks for reference
29	9. Size appropriately: Keep tracks between 1-5 days of work
30	10. Clear acceptance criteria: Every requirement must be testable

People who liked this also viewed

6 picks

Type