Agent skill

Track Manager

by Ibrahim-3d in Ibrahim-3d/orchestrator-supaconductor

Manage Conductor tracks, phases, and tasks. An agent skill from Ibrahim-3d/orchestrator-supaconductor.

AGPL-3.0Auto-check passed

Install Track Manager

skills CLI

$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill track-manager -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Ibrahim-3d/orchestrator-supaconductor track-manager --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/track-manager .claude/skills/track-manager && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "track-manager" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/track-manager into .claude/skills/track-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "track-manager", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/track-manager

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill track-manager -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Ibrahim-3d/orchestrator-supaconductor track-manager --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/track-manager .agents/skills/track-manager && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "track-manager" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/track-manager into .agents/skills/track-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "track-manager", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill track-manager -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Ibrahim-3d/orchestrator-supaconductor track-manager --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/track-manager .cursor/skills/track-manager && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "track-manager" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/track-manager into .cursor/skills/track-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "track-manager", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Ibrahim-3d/orchestrator-supaconductor.git --path skills/track-manager

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill track-manager -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Ibrahim-3d/orchestrator-supaconductor track-manager --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/track-manager .gemini/skills/track-manager && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "track-manager" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/track-manager into .gemini/skills/track-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "track-manager", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Ibrahim-3d/orchestrator-supaconductor track-manager

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill track-manager -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/track-manager .github/skills/track-manager && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "track-manager" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/track-manager into .github/skills/track-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "track-manager", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill track-manager -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Ibrahim-3d/orchestrator-supaconductor track-manager --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/track-manager .opencode/skills/track-manager && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "track-manager" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/track-manager into .opencode/skills/track-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "track-manager", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: track-manager
GitHub stars: 380
Token cost: ~1.5k tokens
SKILL.md length: 389 words
Files: 1
Skills in repo: 27
Repo updated: Sep 27, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

Manage Conductor tracks, phases, and tasks. An agent skill from Ibrahim-3d/orchestrator-supaconductor.

Works in 3 steps: ALWAYS update plan.md after completing… → ALWAYS evaluate before marking anything… → NEVER skip the pre-execution plan…
Working with track status
SKILL.md covers MANDATORY: Evaluate-Loop…, Trigger Conditions, Track Structure and Metadata v2 Protocol, plus 5 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Track Manager is an agent skill from Ibrahim-3d/orchestrator-supaconductor. Manage Conductor tracks, phases, and tasks. Use when working with track status, updating task markers, or navigating between tracks. Enforces the Evaluate-Loop workflow.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Multi-agent orchestration system for Claude Code with parallel execution, automated quality gates, Board of Directors, and bundled Superpowers skills. The licence is AGPL-3.0.

When your agent uses it

Working with track status
Updating task markers
Navigating between tracks

Example prompts

“/track-manager”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

ALWAYS update plan.md after completing any task (prevents duplicate work across sessions)
ALWAYS evaluate before marking anything complete
NEVER skip the pre-execution plan evaluation

What it can do on your machine

Read from SKILL.md and the folder at commit 76c9b10. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Track Manager loads about 1.5k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 389 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~46
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Ibrahim-3d/orchestrator-supaconductor at commit 76c9b10, republished under its AGPL-3.0 licence (© Ibrahim-3d). 389 words, ~1,518 tokens.

Download SKILL.mdSave it as .claude/skills/track-manager/SKILL.md (or your agent's skills folder).

name: track-manager
description: Manage Conductor tracks, phases, and tasks. Use when working with track status, updating task markers, or navigating between tracks. Enforces the Evaluate-Loop workflow.

Track Manager Skill

Manage the lifecycle of Conductor tracks including status updates, task completion, and phase transitions. All operations follow the Evaluate-Loop process defined in conductor/workflow.md.

MANDATORY: Evaluate-Loop Integration

Every track operation must follow the Evaluate-Loop:

PLAN → EVALUATE PLAN → EXECUTE → EVALUATE EXECUTION → COMPLETE/FIX

Key rules:

ALWAYS update plan.md after completing any task (prevents duplicate work across sessions)
ALWAYS evaluate before marking anything complete
NEVER skip the pre-execution plan evaluation

Trigger Conditions

Use this skill when:

Checking track status or progress
Marking tasks as complete
Transitioning between phases
Running pre/post execution evaluations
User mentions: "track status", "mark complete", "next task", "update plan", "evaluate"

Track Structure

conductor/
├── tracks.md           # Master track list
├── authority-matrix.md # Lead Engineer decision boundaries
├── schemas/
│   └── track-metadata.v2.json  # Metadata schema definition
└── tracks/
    └── <track_id>/
        ├── spec.md         # Requirements
        ├── plan.md         # Phased tasks (MUST be kept updated)
        └── metadata.json   # v2 status with loop_state

Metadata v2 Protocol

All tracks use the v2 metadata schema with explicit loop state tracking.

Creating a New Track

Initialize metadata.json with v2 structure:

json

{
  "version": 2,
  "track_id": "feature-name_20260131",
  "type": "feature",
  "status": "new",
  "created_at": "2026-01-31T00:00:00Z",
  "updated_at": "2026-01-31T00:00:00Z",

  "loop_state": {
    "current_step": "PLAN",
    "step_status": "NOT_STARTED",
    "fix_cycle_count": 0,
    "max_fix_cycles": 5,
    "plan_revision_count": 0,
    "max_plan_revisions": 3,
    "checkpoints": {
      "PLAN": { "status": "NOT_STARTED" },
      "EVALUATE_PLAN": { "status": "NOT_STARTED" },
      "EXECUTE": { "status": "NOT_STARTED" },
      "EVALUATE_EXECUTION": { "status": "NOT_STARTED" },
      "FIX": { "status": "NOT_STARTED" },
      "BUSINESS_SYNC": { "status": "NOT_STARTED", "required": false }
    }
  },

  "lead_consultations": [],
  "discovered_work": [],
  "blockers": []
}

Updating Loop State

When a step completes, update the checkpoint:

json

{
  "loop_state": {
    "current_step": "EXECUTE",
    "step_status": "IN_PROGRESS",
    "checkpoints": {
      "PLAN": {
        "status": "PASSED",
        "completed_at": "2026-01-31T10:00:00Z",
        "agent": "loop-planner"
      },
      "EVALUATE_PLAN": {
        "status": "PASSED",
        "completed_at": "2026-01-31T10:30:00Z",
        "verdict": "PASS"
      },
      "EXECUTE": {
        "status": "IN_PROGRESS",
        "started_at": "2026-01-31T11:00:00Z",
        "tasks_completed": 3,
        "tasks_total": 10,
        "last_task": "Task 1.3"
      }
    }
  }
}

Migrating v1 to v2

If a track has v1 metadata (no version field or loop_state):

read_file current metadata fields
Infer loop state from plan.md content
Add v2 structure with inferred values
write_file back to metadata.json

Task Status Markers

Marker	Status	Description
`[ ]`	Pending	Not started
`[~]`	In Progress	Currently working
`[x]`	Completed	Done (add commit SHA + summary)
`[!]`	Blocked	Add note explaining why

Workflow Operations

Before Starting ANY Work

read_file tracks.md to see what's already complete
read_file the track's plan.md to see what tasks are done vs pending
read_file spec.md to understand requirements
Evaluate the plan — verify scope matches spec, no overlap with completed tracks

Show full SKILL.md (145 more words)Show less

Start a Task

markdown

# Before
- [ ] Implement user authentication

# After (mark in progress)
- [~] Implement user authentication

Complete a Task (MANDATORY: update plan.md immediately)

markdown

# After completion (add commit SHA + summary of what was done)
- [x] Implement user authentication <!-- abc1234 -->
  - Created src/components/auth/signup-form.tsx
  - Added email/password validation
  - Integrated with mock API client

Update tracks.md

When completing a phase, update conductor/tracks.md:

markdown

## Active Tracks

| Track ID | Type    | Status      | Progress  |
| -------- | ------- | ----------- | --------- |
| auth-001 | feature | in_progress | Phase 2/3 |

Phase Transition Rules

All tasks in phase must be [x] before moving to next phase
Run post-execution evaluation (see Evaluate-Loop in conductor/workflow.md)
If evaluation fails → create fix tasks → execute → re-evaluate (loop)
If evaluation passes → update metadata.json with completion timestamp
Create commit for phase completion
Update tracks.md progress column
Update conductor/index.md current status

Post-Execution Evaluation Checklist

Before marking a track complete, verify:

Check	Question
Deliverables	Every deliverable in `spec.md` exists and is functional?
Alignment	Implementation matches what was planned (no scope drift)?
No Regressions	Build passes? No console errors? Existing features work?
Quality	Usability check passes on all user-facing copy?
plan.md Updated	All tasks marked `[x]` with summaries?
No Leftover	No tasks skipped or left incomplete?

Response Format

After track operations:

## Track Update

**Track**: [track_id]
**Operation**: [started/completed/updated/evaluated]
**Phase**: [phase number] - [phase name]
**Progress**: [completed]/[total] tasks
**Evaluation**: [PASS / FAIL - describe issues]
**Next**: [next task description]

Files

Just SKILL.md in skills/track-manager of Ibrahim-3d/orchestrator-supaconductor.

Open the folder on GitHubat commit 76c9b10

Compare with similar skills

Track Manager next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Track Manager compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Track Manager this skillIbrahim-3d/orchestrator-supaconductor	380	—	~1.5k	Automated safety check: Pass	AGPL-3.0	11 days ago
Conductor New Trackgemini-cli-extensions/conductor	3.8k	—	~3.6k	Automated safety check: Pass	Apache-2.0	1 mo ago
Conductor Track Managementwshobson/agents	40k	9 repos	~420	Automated safety check: Pass	MIT	3 days ago
Cost Trackingaffaan-m/ECC	275k	1 repos	~1.3k	Automated safety check: Pass	MIT	3 days ago
TrackingBuilderIO/agent-native	7.1k	—	~7.8k	Automated safety check: Pass	None	today
Time Trackingsickn33/agentic-awesome-skills	47k	1 repos	~3.8k	Automated safety check: Pass	MIT	yesterday

Similar skills

Conductor New Track
gemini-cli-extensions/conductor
Plans a new track (feature or bug fix), generates spec/plan documents, and updates the registry.
3.8k GitHub stars~3.6k tokensUpdated 1 mo ago
DevelopmentAuto-check passed
Conductor Track Management
wshobson/agents
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md…
40k GitHub starsUsed in 9 repos~420 tokens
DevelopmentAuto-check passed
Cost Tracking
affaan-m/ECC
Track and report Claude Code token usage, spending, and budgets from the local ECC cost-tracker metrics log.
275k GitHub starsUsed in 1 repo~1.3k tokens
AI & LLM EngineeringAuto-check passed
Tracking
BuilderIO/agent-native
Server-side analytics tracking with pluggable providers. An agent skill from BuilderIO/agent-native.
7.1k GitHub stars~7.8k tokensUpdated today
Backend & APIsAuto-check passed
Time Tracking
sickn33/agentic-awesome-skills
Time entry register: employee, project, client, task, hours, billable flag, rate and amount, invoice and approver.
47k GitHub starsUsed in 1 repo~3.8k tokens
Productivity & AutomationAuto-check passed
Horizon Track
ruvnet/ruflo
Track long-horizon objectives across multiple sessions with milestone checkpoints, progress persistence, and drift detection
74k GitHub stars~744 tokensUpdated today
Product & Project ManagementAuto-check: notes

More from Ibrahim-3d/orchestrator-supaconductor

All 27 skills in this repo

Cto Advisor
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
380 GitHub starsUsed in 4 repos~2.4k tokens
Auto-check passed
Context Driven Development
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…
380 GitHub starsUsed in 9 repos~2.9k tokens
Auto-check passed
Agent Factory
Ibrahim-3d/orchestrator-supaconductor
Creates specialized worker agents dynamically from templates.
380 GitHub stars~2.9k tokensUpdated 11 days ago
Auto-check passed
Board Of Directors
Ibrahim-3d/orchestrator-supaconductor
Simulate a 5-member expert board deliberation for major decisions.
380 GitHub stars~1.9k tokensUpdated 11 days ago
Auto-check passed
Business Docs Sync
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when completing a track that changes pricing, AI models, product features, or asset pipelines — syncs business context documents across all tiers.
380 GitHub stars~2.1k tokensUpdated 11 days ago
Auto-check passed
Context Loader
Ibrahim-3d/orchestrator-supaconductor
Load project context efficiently for Conductor workflows. An agent skill from Ibrahim-3d/orchestrator-supaconductor.
380 GitHub stars~830 tokensUpdated 11 days ago
Auto-check passed

Questions about Track Manager

What does Track Manager do?

Manage Conductor tracks, phases, and tasks. An agent skill from Ibrahim-3d/orchestrator-supaconductor. Track Manager is an agent skill from Ibrahim-3d/orchestrator-supaconductor. Manage Conductor tracks, phases, and tasks.

When should I use Track Manager?

Track Manager fits situations like: working with track status; updating task markers; navigating between tracks.

How do I install Track Manager in Claude Code?

Run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill track-manager -a claude-code`. Or copy the skill folder (skills/track-manager in Ibrahim-3d/orchestrator-supaconductor) into .claude/skills/track-manager in your project. Claude Code loads it when a task matches its description.

How do I install Track Manager in Codex?

Run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill track-manager -a codex`. Or copy the skill folder (skills/track-manager in Ibrahim-3d/orchestrator-supaconductor) into .agents/skills/track-manager in your project. Codex loads it when a task matches its description.

Can I use Track Manager in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill track-manager -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/track-manager, .gemini/skills/track-manager, .github/skills/track-manager and .opencode/skills/track-manager in your project.

What does Track Manager need to run?

SKILL.md names no scripts, command-line tools or credentials: Track Manager is instructions for the agent only.

Does Track Manager access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Track Manager safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Track Manager use?

Track Manager is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Track Manager use?

About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Track Manager?

Skills that share tags, products or a category with Track Manager: Conductor New Track (gemini-cli-extensions/conductor, 3.8k stars), Conductor Track Management (wshobson/agents, 40k stars), Cost Tracking (affaan-m/ECC, 275k stars) and Tracking (BuilderIO/agent-native, 7.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Track Manager?

Ibrahim-3d (a GitHub user) maintains it in Ibrahim-3d/orchestrator-supaconductor, which has 380 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on September 27, 2026.

Source: Ibrahim-3d/orchestrator-supaconductor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Track Manager

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Track Manager Skill

MANDATORY: Evaluate-Loop Integration

Trigger Conditions

Track Structure

Metadata v2 Protocol

Creating a New Track

Updating Loop State

Migrating v1 to v2

Task Status Markers

Workflow Operations

Before Starting ANY Work

Start a Task

Complete a Task (MANDATORY: update plan.md immediately)

Update tracks.md

Phase Transition Rules

Post-Execution Evaluation Checklist

Response Format

Files

Compare with similar skills

Similar skills

More from Ibrahim-3d/orchestrator-supaconductor

Questions about Track Manager