Pick Up API Task from Coordinator

Accept an API-layer plan from the coordinator, implement it following conventions and contracts, then verify with build and tests.

Sby Skills Guide Bot
DevelopmentIntermediate
107/23/2026
Claude Code
#api#task-pickup#clean-architecture#dotnet#verification

Recommended for


name: pickup-task description: Accept and implement an API-layer plan from the coordinator user-invocable: true

Pickup Task from Coordinator

You are receiving a plan scoped to the API layer.

Steps

  1. Read the plan. User provides it inline or as a file path.
  2. Review conventions. Re-read CLAUDE.md (Clean Architecture, DI, DTO naming).
  3. Check contracts. Read ../patient-care-super/_contracts/ for API shapes to match.
  4. Check for existing branch: git branch -a | grep -E "feature/|fix/" — reuse if one exists.
  5. Create branch if needed: feature/<desc> or fix/<desc>. Never commit to main.
  6. Kanban — Move related card to DOING:
    curl -s --max-time 2 -X POST http://openclaw:8082/api/move \
      -H "Content-Type: application/json" -d '{"cardId": <ID>, "columnId": 4}'
    
  7. Implement. Only API-layer steps. Follow existing patterns when referenced.
  8. Verify:
    dotnet build patient-care-api.sln
    dotnet test patient-care-api.sln
    
  9. Test artifact: Produce curl commands for each new/modified endpoint.
  10. Commit with a clear message.
  11. Record completion. Append to the plan file in ../patient-care-super/planning/active/:
    ## Completion — API
    - **Date**: YYYY-MM-DD
    - **Branch**: `feature/branch-name`
    - **Verification**: build: PASS/FAIL | test: PASS/FAIL
    - **Files**: N created, M modified
    - **Test artifact**: [curl commands]
    - **Open items**: None
    
    If other layers pending, leave in active/. If all done, move to completed/ + add to archive.md (uncommitted).
  12. Report back. Summarize implementation, verification, and open questions.
Related skills