| name | implement |
| description | Implement features, fix bugs, and modify production source code in S3Mock. Use when asked to add functionality, change behavior, or modify source files in server/, integration-tests/, or testsupport/. Not for documentation-only or test-only changes. Orchestrates lint, test, and document skills as part of the complete workflow. |
Implementation Skill
Entry Criteria
Use for new functionality, bug fixes, or behavior changes in server/, integration-tests/, or testsupport/. Not for test-only or documentation-only changes — use the test or document skill instead.
Before Starting
- Read root
AGENTS.md and the relevant module AGENTS.md (server/AGENTS.md, integration-tests/AGENTS.md, or testsupport/AGENTS.md).
- For a new S3 operation, verify element names and behavior against the AWS S3 API docs.
- Review existing similar implementations for patterns to follow.
- If nearby code would benefit from cleanup before adding new code, invoke the
refactor skill first.
Execution Steps
- For a new S3 operation, follow server/AGENTS.md § Implementation Flow (DTO → Store → Service → Controller → IT) — do not skip layers or add logic in the wrong layer.
- Update the copyright year in every modified file (
INVARIANTS.md).
- Invoke the
lint skill.
- Invoke the
test skill to add or update unit and integration tests.
- Invoke the
document skill to update CHANGELOG.md, README.md, and AGENTS.md where applicable.
Completion Criteria
Troubleshooting
- Build fails: confirm JDK 25 is active; run
make format and fix remaining lint errors.
- XML test failures: a compile check is not sufficient (
INVARIANTS.md) — run integration tests to confirm serialized output.
- Docker fails: use
make skip-docker to isolate the build from Docker issues.
Resources
AGENTS.md, INVARIANTS.md- Relevant module
AGENTS.md (server/AGENTS.md, integration-tests/AGENTS.md, or testsupport/AGENTS.md)
