pickup-task
Executes API-specific development plans by following architecture and contract guidelines.
Install
mkdir -p .claude/skills/pickup-task && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12083" && unzip -o skill.zip -d .claude/skills/pickup-task && rm skill.zipInstalls to .claude/skills/pickup-task
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Accept and implement an API-layer plan from the coordinatorKey capabilities
- →Read and understand an API-layer implementation plan.
- →Review architectural conventions and API contracts.
- →Create a new feature or fix branch, or reuse an existing one.
- →Implement API-layer tasks following existing patterns.
- →Verify implementation with `dotnet build` and `dotnet test`.
How it works
The skill takes an API-layer plan, creates a development branch, implements the specified tasks, verifies the changes with builds and tests, and records the completion.
Inputs & outputs
When to use pickup-task
- →Developing new API endpoints
- →Applying API-layer fixes
- →Following implementation plans
About this skill
Pickup Task from Coordinator
You are receiving a plan scoped to the API layer.
Steps
- Read the plan. User provides it inline or as a file path.
- Conventions (Clean Architecture, DI, DTO naming) are in the auto-loaded
CLAUDE.md— don't re-read it. - Check contracts. List
../patient-care-super/_contracts/filenames, then read only the contract file(s) for the domain(s) the plan touches (e.g.sessions-api.mdfor session work) — never the whole directory. - Check for existing branch:
git branch -a | grep -E "feature/|fix/"— reuse if one exists. - Create branch if needed:
feature/<desc>orfix/<desc>. Never commit to main. - 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}' - Implement. Only API-layer steps. Follow existing patterns when referenced.
- Verify:
dotnet build patient-care-api.sln dotnet test patient-care-api.sln - Test artifact: Produce curl commands for each new/modified endpoint.
- Commit with a clear message.
- Record completion. Append to the plan file in
../patient-care-super/planning/active/:
If other layers pending, leave in## 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**: Noneactive/. If all done, move tocompleted/+ add toarchive.md(uncommitted). - Report back. Summarize implementation, verification, and open questions.
When not to use it
- →When the plan is not scoped to the API layer.
- →When the user wants to commit directly to the `main` branch.
- →When the user does not want to verify with builds and tests.
Limitations
- →The plan must be scoped to the API layer.
- →Commits are never made directly to the `main` branch.
- →Requires `dotnet build` and `dotnet test` for verification.
How it compares
This skill provides a structured workflow for API-layer development, ensuring adherence to conventions, contract checks, and verification steps, unlike an unguided implementation.
Compared to similar skills
pickup-task side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| pickup-task (this skill) | 0 | 4mo | Review | Intermediate |
| dotnet-backend-patterns | 7 | 5mo | No flags | Advanced |
| azure-maps-search-dotnet | 2 | 3mo | Review | Intermediate |
| azure-servicebus-dotnet | 3 | 3mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
dotnet-backend-patterns
wshobson
Master C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuration, caching, and testing with xUnit. Use when developing .NET backends, reviewing C# code, or designing API architectures.
azure-maps-search-dotnet
microsoft
Azure Maps SDK for .NET. Location-based services including geocoding, routing, rendering, geolocation, and weather. Use for address search, directions, map tiles, IP geolocation, and weather data. Triggers: "Azure Maps", "MapsSearchClient", "MapsRoutingClient", "MapsRenderingClient", "geocoding .NET", "route directions", "map tiles", "geolocation".
azure-servicebus-dotnet
microsoft
Azure Service Bus SDK for .NET. Enterprise messaging with queues, topics, subscriptions, and sessions. Use for reliable message delivery, pub/sub patterns, dead letter handling, and background processing. Triggers: "Service Bus", "ServiceBusClient", "ServiceBusSender", "ServiceBusReceiver", "ServiceBusProcessor", "message queue", "pub/sub .NET", "dead letter queue".
m365-agents-dotnet
microsoft
Microsoft 365 Agents SDK for .NET. Build multichannel agents for Teams/M365/Copilot Studio with ASP.NET Core hosting, AgentApplication routing, and MSAL-based auth. Triggers: "Microsoft 365 Agents SDK", "Microsoft.Agents", "AddAgentApplicationOptions", "AgentApplication", "AddAgentAspNetAuthentication", "Copilot Studio client", "IAgentHttpAdapter".
azure-eventgrid-dotnet
microsoft
Azure Event Grid SDK for .NET. Client library for publishing and consuming events with Azure Event Grid. Use for event-driven architectures, pub/sub messaging, CloudEvents, and EventGridEvents. Triggers: "Event Grid", "EventGridPublisherClient", "CloudEvent", "EventGridEvent", "publish events .NET", "event-driven", "pub/sub".
azure-mgmt-mongodbatlas-dotnet
microsoft
Manage MongoDB Atlas Organizations as Azure ARM resources using Azure.ResourceManager.MongoDBAtlas SDK. Use when creating, updating, listing, or deleting MongoDB Atlas organizations through Azure Marketplace integration. This SDK manages the Azure-side organization resource, not Atlas clusters/databases directly.