Track Management

When creating, managing, or working with Conductor tracks: the logical work units for…

A disciplined system for turning features, bugs, and refactors into trackable work units, each with its own spec, phased plan, and metadata. It enforces clear scope boundaries, atomic tasks tied to commit SHAs, and a status-marker convention so you always know exactly what is done, in progress, blocked, or skipped. Work becomes git-aware and revertable at the track, phase, or task level.

$15 one-time
Add to a kit →

Prices include 20% VAT. · Forged on real agency work · one-time, no lock-in

  • Type Skill
  • Category Development
  • Delivery Email · instant
  • License One-time
Run preview
forgehouse, track-management

Inside the run · no black box

See the actual work before you buy it.

A track that cannot fit in five days is two tracks. Between that sizing rule and the final archive, every Conductor track passes through the same gated lifecycle:

  1. Creates the track through interactive Q&A: gathers requirements, acceptance criteria, scope boundaries and dependencies, then generates a structured spec.md (functional and non-functional requirements, explicit in-scope and out-of-scope lists, a risk table and open questions).
  2. Generates plan.md as a phased breakdown: tasks grouped into 2-4 phases, each phase ending in verification tasks, with a checkpoint SHA table. Sizing is enforced up front: a track should fit 1-5 days; 5+ phases or 25+ tasks means split into separate tracks.
  3. Registers the track in tracks.md with a {shortname}_{YYYYMMDD} ID and writes metadata.json carrying status, phase and task counters.
  4. Executes implementation with strict status markers: a task moves from pending to in-progress, gets implemented TDD-first, then is marked complete with its commit SHA recorded inline, so every line of work is traceable to a commit. Blocked tasks carry an explicit reason, skipped tasks an explicit justification.
  5. Closes each phase through a gate: all tasks checked, verification tasks done, checkpoint approval received and the checkpoint SHA recorded before the next phase may start. Phase order follows the dependency direction (schema before logic before UI), never reversed.
  6. Completes the track only when every acceptance criterion is checked, product and tech-stack docs are synced, tracks.md and metadata.json are updated, and the track is archived rather than deleted so it stays revertible at track, phase or task granularity.
Use cases · what happens when you plug it in

One power source. 6 lines out.

track-management · core

core active · 6 lines

  1. Breaking a feature into spec.md + phased plan.md

    ✓ breaking a feature into
  2. Tracking bug fixes from reproduction test to verification

    ✓ tracking bug fixes from
  3. Managing a track registry across an active backlog

    ✓ managing a track registry
  4. Recording commit SHAs for per-task traceability

    ✓ recording commit shas for
  5. Reverting a unit of work cleanly by track or phase

    ✓ reverting a unit of work
  6. Right-sizing work to avoid oversized, unmergeable changes

    ✓ right-sizing work to avoid
Benefits · what you walk away with

Yours to keep.

Drag time forward. Watch what stays.

Forever

That's what owning means.

The rented stack

ai writing tool: subscription

expired · access lost

analytics suite: subscription

expired · access lost

design platform: subscription

expired · access lost

(nothing left)

Your forge

  1. Every requirement maps to a testable acceptance criterion before code starts

    license: perpetual
  2. Scope creep is caught early with explicit in-scope and out-of-scope sections

    license: perpetual
  3. Stalled work is visible: blocked tasks carry their reason inline

    license: perpetual
  4. Reverting is surgical instead of risky, thanks to SHA-level tracking

    license: perpetual

subscriptions expire · deeds don't

What's included · the full manifest

Everything in the box.

Pick a piece up. Watch it work.

spec.md structure with functional/non-functional requirements and risk table

part 01 of 06 · in the box

6 parts · one working system · ships instantly by email

Who it's for

This wasn't forged for everyone.

  • Not for you if you'd rather rent a tool than own one.
  • Not for you if you want someone else to run your stack.
  • Not for you if you're happy guessing.
Still here? Good.

Engineering teams and solo builders who want feature and bug work organized into spec-driven, revertable, traceable units instead of loose commits.

then this was forged for you.

Works with

Universal by design: these run in any AI. Delivered in the open Agent Skills + MCP format (native in Claude); ChatGPT, Gemini, Cursor and Copilot adapt the same files their own way.

  • Claude Native format
  • ChatGPT Adapts via open standards
  • Gemini Adapts via open standards
  • Cursor Adapts via open standards
  • Copilot Adapts via open standards
Questions · still in the air

Catch what's on your mind.

the air is clear. nothing between you and the forge.
catch a spark: the forge will answer

  1. Is this overkill for a solo developer, or only useful for teams?

    The sizing guideline: one to five days, two to four phases, eight to twenty tasks per track, works at solo scale too; the spec and plan files mainly stop you from drifting on your own work. Teams get the extra benefit of the shared tracks.md registry and visible blocked-task reasons.

  2. What makes reverting 'surgical' instead of just running git revert and hoping?

    Every atomic task records its commit SHA in the track metadata, and the plan is split into phases with verification gates between them. So you can revert one task, one phase or the whole track as a known set of commits instead of hunting through the log for what belonged to the feature.

  3. Does it replace Jira or another project management tool?

    No. It is a file-based convention, spec.md, plan.md, tracks.md and metadata.json living in your repo for Conductor tracks: with no boards, notifications or assignee workflows. It organizes the engineering unit of work; team-level project tooling is a different layer.

  4. How is it delivered?

    By email right after purchase: ready to run, downloaded instantly, no setup wait.

  5. One-time or subscription?

    A one-time purchase; no subscription or hidden fees. VAT (20%) is included.

  6. Can I get a refund?

    As a digital product, it can’t be refunded once downloaded. That’s why we show exactly what’s inside and who it’s for, right here.