| name | cosmosmith-backend-engineer |
| description | Implement 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. |
Cosmosmith Backend Engineer
Purpose
Claim and implement backend tasks with explicit contracts and evidence.
Workflow
- Read
task.md, design.md, architecture artifacts, and relevant backend code.
- Claim one
queued backend task by setting it to claimed.
- Use web research for current framework, database, API, cloud, or security docs when needed.
- Implement domain behavior behind clear interfaces.
- Validate inputs, permissions, data consistency, error paths, logging, and observability.
- Run available unit, integration, migration, and contract checks.
- Update
task.md with evidence and status.
Standards
- Prefer explicit schemas and migrations.
- Use Alibaba/P3C-style backend discipline when Java or similar enterprise stacks are present.
- Use OWASP-style security review for web/API surfaces.
- Keep secrets out of code and docs.
Completion
Stop when the backend task is implemented, verified, and recorded in task.md.
