gh-dhruvbaldawa-ccconfigs-experimental/skills/implementing-tasks/SKILL.md

name, description

name	description
implementing-tasks	Implements tasks from .plans/ directories by following implementation guidance, writing code and tests, and updating task status. Use when task file is in implementation/ directory and requires code implementation with comprehensive testing. Launches research agents when stuck.

Implementation

Given task file path .plans/<project>/implementation/NNN-task.md:

Process

Use TodoWrite to track implementation progress:

☐ Read task file (LLM Prompt, Working Result, Validation)
☐ [LLM Prompt step 1]
☐ [LLM Prompt step 2]
...
☐ Write tests for new functionality
☐ Run full test suite
☐ Mark validation checkboxes
☐ Update status to READY_FOR_REVIEW

Convert each step from the task's LLM Prompt into a todo. Mark completed as you progress.

1. Read task file - LLM Prompt, Working Result, Validation, Files
2. Follow LLM Prompt step-by-step, write code + tests, run full suite
3. Update task status using Edit tool:
   • Find: **Status:** [current status]
   • Replace: **Status:** READY_FOR_REVIEW
4. Append implementation notes using bash:

   cat >> "$task_file" <<EOF
   
   **implementation:**
   - Followed LLM Prompt steps 1-N
   - Implemented [key functionality]
   - Added [N] tests: all passing
   - Full test suite: [M]/[M] passing
   - Working Result verified: ✓ [description]
   - Files: [list with brief descriptions]
   EOF
   

5. Mark validation checkboxes: [ ] → [x] using Edit tool
6. Report completion

Stuck Handling

When blocked during implementation:

1. Mark Task as Stuck

• Update status using Edit tool:
  • Find: **Status:** [current status]
  • Replace: **Status:** STUCK
• Append notes:

  cat >> "$task_file" <<EOF
  
  **implementation:**
  - Attempted [what tried]
  - BLOCKED: [specific issue]
  - Launching research agents to investigate...
  EOF
  

2. Launch Research Agents

Based on blocker type, launch 2-3 agents in parallel:

New technology/framework → research-breadth + research-technical:

• research-breadth: General understanding of technology/approach
• research-technical: Official API documentation

Specific error/issue → research-depth + research-technical:

• research-depth: Detailed analysis of specific solutions
• research-technical: Official API documentation

API integration → research-technical + research-depth:

• research-technical: Official API documentation
• research-depth: Detailed implementation examples

Best practices/patterns → research-breadth + research-depth:

• research-breadth: General surveys and comparisons
• research-depth: Detailed analysis of specific approaches

Example:

# Launch agents with specific questions
research-breadth "How to [solve blocker]?"
research-depth "Detailed solutions for [specific issue]"
research-technical "[library/framework] official documentation for [feature]"

3. Synthesize Findings

Use research-synthesis skill (from essentials) to:

• Consolidate findings from all agents
• Identify concrete path forward
• Extract actionable implementation guidance

Update task file with research findings:

cat >> "$task_file" <<EOF

**research findings:**
- [Agent 1]: [key insights]
- [Agent 2]: [key insights]
- [Agent 3]: [key insights]

**resolution:**
[Concrete path forward based on research]
EOF

4. Continue or Escalate

If unblocked:

• Update status back to IN_PROGRESS
• Resume implementation following research guidance
• Complete normally as per main Process section

If still stuck after research:

• Keep status as STUCK
• Append escalation notes
• STOP and report blocker with research context

cat >> "$task_file" <<EOF

**escalation:**
- Research completed but blocker remains
- Reason: [why research didn't unblock]
- Need: [what's needed - human decision, missing requirement, etc.]
EOF

Then STOP and report blocker with full context.

Rejection Handling

If task moved back from review:

1. Read review notes for issues
2. Fix all blocking issues
3. Update status to READY_FOR_REVIEW again
4. Append revision notes:

   **implementation (revision):**
   - Fixed [issue 1]
   - Fixed [issue 2]
   - Re-ran tests: [M]/[M] passing