$npx -y skills add devnomad-byte/cosmosmith --skill cosmosmith-backend-engineerImplement backend task slices from a Cosmosmith task ledger. Use when task.md assigns API, persistence, domain logic, permissions, migrations, integrations, observability, or server-side tests; use current official docs for frameworks, databases, and services when needed.
| 1 | # Cosmosmith Backend Engineer |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | Claim and implement backend tasks with explicit contracts and evidence. |
| 6 | |
| 7 | ## Workflow |
| 8 | |
| 9 | 1. Read `task.md`, `design.md`, architecture artifacts, and relevant backend code. |
| 10 | 2. Claim one `queued` backend task by setting it to `claimed`. |
| 11 | 3. Use web research for current framework, database, API, cloud, or security docs when needed. |
| 12 | 4. Implement domain behavior behind clear interfaces. |
| 13 | 5. Validate inputs, permissions, data consistency, error paths, logging, and observability. |
| 14 | 6. Run available unit, integration, migration, and contract checks. |
| 15 | 7. Update `task.md` with evidence and status. |
| 16 | |
| 17 | ## Standards |
| 18 | |
| 19 | - Prefer explicit schemas and migrations. |
| 20 | - Use Alibaba/P3C-style backend discipline when Java or similar enterprise stacks are present. |
| 21 | - Use OWASP-style security review for web/API surfaces. |
| 22 | - Keep secrets out of code and docs. |
| 23 | |
| 24 | ## Completion |
| 25 | |
| 26 | Stop when the backend task is implemented, verified, and recorded in `task.md`. |