From gilfoyle
Manage Conductor tracks, phases, and tasks. Use when working with track status, updating task markers, or navigating between tracks. Enforces the Evaluate-Loop workflow.
npx claudepluginhub ahmedelhadarey/gilfoyle --plugin gilfoyleThis skill uses the workspace's default tool permissions.
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`.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
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.
Every track operation must follow the Evaluate-Loop:
PLAN → EVALUATE PLAN → EXECUTE → EVALUATE EXECUTION → COMPLETE/FIX
Key rules:
plan.md after completing any task (prevents duplicate work across sessions)Use this skill when:
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
All tracks use the v2 metadata schema with explicit loop state tracking.
Initialize metadata.json with v2 structure:
{
"version": 4,
"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": 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": []
}
When a step completes, update the checkpoint:
{
"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"
}
}
}
}
If a track has v1 metadata (no version field or loop_state):
| Marker | Status | Description |
|---|---|---|
[ ] | Pending | Not started |
[~] | In Progress | Currently working |
[x] | Completed | Done (add commit SHA + summary) |
[!] | Blocked | Add note explaining why |
tracks.md to see what's already completeplan.md to see what tasks are done vs pendingspec.md to understand requirements# Before
- [ ] Implement user authentication
# After (mark in progress)
- [~] Implement user authentication
# 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
When completing a phase, update conductor/tracks.md:
## Active Tracks
| Track ID | Type | Status | Progress |
| -------- | ------- | ----------- | --------- |
| auth-001 | feature | in_progress | Phase 2/3 |
[x] before moving to next phaseconductor/workflow.md)metadata.json with completion timestamptracks.md progress columnconductor/index.md current statusBefore 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? |
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]