composed-changes-implement

To implement a user story ticket, follow a structured workflow that verifies pre-requisite documents, writes code, runs unit tests, updates architecture.md, and commits changes. This skill automates the entire process.

Before implementing a user story, you need three pre-requisite documents: requirements.md, architecture.md, and ticket.md. The structured implementation workflow verifies these files exist before proceeding.

Automating code implementation and unit testing requires a structured workflow that ingests ticket details, writes the code, and executes validation steps. This skill integrates linting, testing, and commit procedures automatically.

Yes, the implementation workflow updates architecture documentation automatically. After validating code changes against the user story, the process modifies architecture.md to reflect the newly implemented features before committing.

No, you cannot use this workflow without pre-defined requirements. The implementation process explicitly requires requirements.md, architecture.md, and ticket.md to exist beforehand to ensure structured and validated development.