[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-b6ff51ce-bb1b-4f54-b112-6f0d8e282811":3,"$fszSk2esZTKroEgm8MDYGNysXtAgxBcbHENpeJ8Vo494":43},{"id":4,"title":5,"description":6,"categoryId":7,"moduleId":8,"tags":9,"prompt":10,"icon":11,"source":12,"sourceUrl":13,"authorId":14,"authorName":15,"isPublic":16,"stars":17,"runs":18,"createdAt":19,"updatedAt":19,"module":20,"category":27,"packages":34},"b6ff51ce-bb1b-4f54-b112-6f0d8e282811","conductor-implement","根据TDD工作流程执行实施计划的任务","cat_coding_review","mod_coding","sickn33,coding","---\nname: conductor-implement\ndescription: \"Execute tasks from a track's implementation plan following TDD workflow\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Implement Track\n\nExecute tasks from a track's implementation plan, following the workflow rules defined in `conductor\u002Fworkflow.md`.\n\n## Use this skill when\n\n- Working on implement track tasks or workflows\n- Needing guidance, best practices, or checklists for implement track\n\n## Do not use this skill when\n\n- The task is unrelated to implement track\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\n## Pre-flight Checks\n\n1. Verify Conductor is initialized:\n   - Check `conductor\u002Fproduct.md` exists\n   - Check `conductor\u002Fworkflow.md` exists\n   - Check `conductor\u002Ftracks.md` exists\n   - If missing: Display error and suggest running `\u002Fconductor:setup` first\n\n2. Load workflow configuration:\n   - Read `conductor\u002Fworkflow.md`\n   - Parse TDD strictness level\n   - Parse commit strategy\n   - Parse verification checkpoint rules\n\n## Track Selection\n\n### If argument provided:\n\n- Validate track exists: `conductor\u002Ftracks\u002F{argument}\u002Fplan.md`\n- If not found: Search for partial matches, suggest corrections\n\n### If no argument:\n\n1. Read `conductor\u002Ftracks.md`\n2. Parse for incomplete tracks (status `[ ]` or `[~]`)\n3. Display selection menu:\n\n   ```\n   Select a track to implement:\n\n   In Progress:\n   1. [~] auth_20250115 - User Authentication (Phase 2, Task 3)\n\n   Pending:\n   2. [ ] nav-fix_20250114 - Navigation Bug Fix\n   3. [ ] dashboard_20250113 - Dashboard Feature\n\n   Enter number or track ID:\n   ```\n\n## Context Loading\n\nLoad all relevant context for implementation:\n\n1. Track documents:\n   - `conductor\u002Ftracks\u002F{trackId}\u002Fspec.md` - Requirements\n   - `conductor\u002Ftracks\u002F{trackId}\u002Fplan.md` - Task list\n   - `conductor\u002Ftracks\u002F{trackId}\u002Fmetadata.json` - Progress state\n\n2. Project context:\n   - `conductor\u002Fproduct.md` - Product understanding\n   - `conductor\u002Ftech-stack.md` - Technical constraints\n   - `conductor\u002Fworkflow.md` - Process rules\n\n3. Code style (if exists):\n   - `conductor\u002Fcode_styleguides\u002F{language}.md`\n\n## Track Status Update\n\nUpdate track to in-progress:\n\n1. In `conductor\u002Ftracks.md`:\n   - Change `[ ]` to `[~]` for this track\n\n2. In `conductor\u002Ftracks\u002F{trackId}\u002Fmetadata.json`:\n   - Set `status: \"in_progress\"`\n   - Update `updated` timestamp\n\n## Task Execution Loop\n\nFor each incomplete task in plan.md (marked with `[ ]`):\n\n### 1. Task Identification\n\nParse plan.md to find next incomplete task:\n\n- Look for lines matching `- [ ] Task X.Y: {description}`\n- Track current phase from structure\n\n### 2. Task Start\n\nMark task as in-progress:\n\n- Update plan.md: Change `[ ]` to `[~]` for current task\n- Announce: \"Starting Task X.Y: {description}\"\n\n### 3. TDD Workflow (if TDD enabled in workflow.md)\n\n**Red Phase - Write Failing Test:**\n\n```\nFollowing TDD workflow for Task X.Y...\n\nStep 1: Writing failing test\n```\n\n- Create test file if needed\n- Write test(s) for the task functionality\n- Run tests to confirm they fail\n- If tests pass unexpectedly: HALT, investigate\n\n**Green Phase - Implement:**\n\n```\nStep 2: Implementing minimal code to pass test\n```\n\n- Write minimum code to make test pass\n- Run tests to confirm they pass\n- If tests fail: Debug and fix\n\n**Refactor Phase:**\n\n```\nStep 3: Refactoring while keeping tests green\n```\n\n- Clean up code\n- Run tests to ensure still passing\n\n### 4. Non-TDD Workflow (if TDD not strict)\n\n- Implement the task directly\n- Run any existing tests\n- Manual verification as needed\n\n### 5. Task Completion\n\n**Commit changes** (following commit strategy from workflow.md):\n\n```bash\ngit add -A\ngit commit -m \"{commit_prefix}: {task description} ({trackId})\"\n```\n\n**Update plan.md:**\n\n- Change `[~]` to `[x]` for completed task\n- Commit plan update:\n\n```bash\ngit add conductor\u002Ftracks\u002F{trackId}\u002Fplan.md\ngit commit -m \"chore: mark task X.Y complete ({trackId})\"\n```\n\n**Update metadata.json:**\n\n- Increment `tasks.completed`\n- Update `updated` timestamp\n\n### 6. Phase Completion Check\n\nAfter each task, check if phase is complete:\n\n- Parse plan.md for phase structure\n- If all tasks in current phase are `[x]`:\n\n**Run phase verification:**\n\n```\nPhase {N} complete. Running verification...\n```\n\n- Execute verification tasks listed for the phase\n- Run full test suite: `npm test` \u002F `pytest` \u002F etc.\n\n**Report and wait for approval:**\n\n```\nPhase {N} Verification Results:\n- All phase tasks: Complete\n- Tests: {passing\u002Ffailing}\n- Verification: {pass\u002Ffail}\n\nApprove to continue to Phase {N+1}?\n1. Yes, continue\n2. No, there are issues to fix\n3. Pause implementation\n```\n\n**CRITICAL: Wait for explicit user approval before proceeding to next phase.**\n\n## Error Handling During Implementation\n\n### On Tool Failure\n\n```\nERROR: {tool} failed with: {error message}\n\nOptions:\n1. Retry the operation\n2. Skip this task and continue\n3. Pause implementation\n4. Revert current task changes\n```\n\n- HALT and present options\n- Do NOT automatically continue\n\n### On Test Failure\n\n```\nTESTS FAILING after Task X.Y\n\nFailed tests:\n- {test name}: {failure reason}\n\nOptions:\n1. Attempt to fix\n2. Rollback task changes\n3. Pause for manual intervention\n```\n\n### On Git Failure\n\n```\nGIT ERROR: {error message}\n\nThis may indicate:\n- Uncommitted changes from outside Conductor\n- Merge conflicts\n- Permission issues\n\nOptions:\n1. Show git status\n2. Attempt to resolve\n3. Pause for manual intervention\n```\n\n## Track Completion\n\nWhen all phases and tasks are complete:\n\n### 1. Final Verification\n\n```\nAll tasks complete. Running final verification...\n```\n\n- Run full test suite\n- Check all acceptance criteria from spec.md\n- Generate verification report\n\n### 2. Update Track Status\n\nIn `conductor\u002Ftracks.md`:\n\n- Change `[~]` to `[x]` for this track\n- Update the \"Updated\" column\n\nIn `conductor\u002Ftracks\u002F{trackId}\u002Fmetadata.json`:\n\n- Set `status: \"complete\"`\n- Set `phases.completed` to total\n- Set `tasks.completed` to total\n- Update `updated` timestamp\n\nIn `conductor\u002Ftracks\u002F{trackId}\u002Fplan.md`:\n\n- Update header status to `[x] Complete`\n\n### 3. Documentation Sync Offer\n\n```\nTrack complete! Would you like to sync documentation?\n\nThis will update:\n- conductor\u002Fproduct.md (if new features added)\n- conductor\u002Ftech-stack.md (if new dependencies added)\n- README.md (if applicable)\n\n1. Yes, sync documentation\n2. No, skip\n```\n\n### 4. Cleanup Offer\n\n```\nTrack {trackId} is complete.\n\nCleanup options:\n1. Archive - Move to conductor\u002Ftracks\u002F_archive\u002F\n2. Delete - Remove track directory\n3. Keep - Leave as-is\n```\n\n### 5. Completion Summary\n\n```\nTrack Complete: {track title}\n\nSummary:\n- Track ID: {trackId}\n- Phases completed: {N}\u002F{N}\n- Tasks completed: {M}\u002F{M}\n- Commits created: {count}\n- Tests: All passing\n\nNext steps:\n- Run \u002Fconductor:status to see project progress\n- Run \u002Fconductor:new-track for next feature\n```\n\n## Progress Tracking\n\nMaintain progress in `metadata.json` throughout:\n\n```json\n{\n  \"id\": \"auth_20250115\",\n  \"title\": \"User Authentication\",\n  \"type\": \"feature\",\n  \"status\": \"in_progress\",\n  \"created\": \"2025-01-15T10:00:00Z\",\n  \"updated\": \"2025-01-15T14:30:00Z\",\n  \"current_phase\": 2,\n  \"current_task\": \"2.3\",\n  \"phases\": {\n    \"total\": 3,\n    \"completed\": 1\n  },\n  \"tasks\": {\n    \"total\": 12,\n    \"completed\": 7\n  },\n  \"commits\": [\n    \"abc1234: feat: add login form (auth_20250115)\",\n    \"def5678: feat: add password validation (auth_20250115)\"\n  ]\n}\n```\n\n## Resumption\n\nIf implementation is paused and resumed:\n\n1. Load `metadata.json` for current state\n2. Find current task from `current_task` field\n3. Check if task is `[~]` in plan.md\n4. Ask user:\n\n   ```\n   Resuming track: {title}\n\n   Last task in progress: Task {X.Y}: {description}\n\n   Options:\n   1. Continue from where we left off\n   2. Restart current task\n   3. Show progress summary first\n   ```\n\n## Critical Rules\n\n1. **NEVER skip verification checkpoints** - Always wait for user approval between phases\n2. **STOP on any failure** - Do not attempt to continue past errors\n3. **Follow workflow.md strictly** - TDD, commit strategy, and verification rules are mandatory\n4. **Keep plan.md updated** - Task status must reflect actual progress\n5. **Commit frequently** - Each task completion should be committed\n6. **Track all commits** - Record commit hashes in metadata.json for potential revert\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","","imported","https:\u002F\u002Fgithub.com\u002Fsickn33\u002Fantigravity-awesome-skills","user_system_seed","SkillOPIC",true,75,913,"2026-05-16 13:12:35",{"id":8,"name":21,"slug":22,"icon":23,"description":24,"sort":25,"createdAt":26},"编程开发","coding","mdi-code-braces","代码生成、调试、审查，提升开发效率",2,"2026-05-16 12:53:40",{"id":7,"name":28,"slug":29,"icon":30,"description":31,"moduleId":8,"sort":32,"skillCount":33,"createdAt":26},"代码审查","review","mdi-magnify-scan","代码质量分析、安全审查",4,145,[35],{"id":36,"skillId":4,"version":37,"fileName":38,"fileSize":39,"filePath":40,"fileHash":41,"manifest":42,"createdAt":19},"208cfcab-5802-4cbe-932e-2100d81799b3","1.0.0","conductor-implement.zip",3644,"uploads\u002Fskills\u002Fb6ff51ce-bb1b-4f54-b112-6f0d8e282811\u002Fconductor-implement.zip","9a7e0f3dfeb25c6f463a33bf68b2d40ac303d4b6f896155819be7886ff176c15","[{\"path\":\"SKILL.md\",\"isDirectory\":false,\"size\":8838}]",{"code":44,"message":45,"data":46},200,"success",{"items":47,"stats":48,"page":51},[],{"averageRating":49,"totalRatings":49,"ratingCounts":50},0,[49,49,49,49,49],{"limit":52,"offset":49,"hasMore":53,"nextOffset":52,"ratedOnly":16},15,false]