Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
When creating, managing, or working with Conductor tracks (logical work units for features, bugs, refactors), including writing spec.md/plan.md, tracking lifecycle, or interpreting track status.
references/details.md for detailed patternsA structured track with clear spec, phased plan, status markers, and archived history that keeps feature/bug/refactor work traceable and verifiable.
Use Cases
A PM starts a new feature and uses this skill to create a Conductor track: writes spec.md with testable acceptance criteria, breaks it into 3-5 task phases in plan.md, and registers it in tracks.md. As engineers work, they mark status and record commit SHAs. Result: clear scope, traceable progress, and a verifiable feature delivery.
A developer picks up a bug track, reviews its spec and plan, follows phase verification tasks, and updates markers immediately on completion while noting SHAs. On finish, the track is archived not deleted. Value: bug fix is reproducible, dependencies explicit, and team retains historical context for future reference.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
Skill File