Implement

Workflow: Implement

Build the solution for a planned ticket.

When to Use

• Ticket is in in-progress with a plan (or is simple enough to skip planning)
• Code changes are needed in the target repo

Inputs

• Issue identifier, title, and description
• Plan document (if exists) at .ai/projects/cascadeguard/plans/ (relative to workspace root)
• The target repo’s codebase

Steps

1. Read the plan — if one exists at .ai/projects/cascadeguard/plans/<identifier>-*.md, follow it
2. Read existing code — understand the current implementation before changing anything
3. Write tests first — add tests for the new/changed behaviour before implementing
4. Implement — make the minimal changes needed. Follow existing patterns and conventions in the repo
5. Run checks locally:
   • Lint and type check (if available)
   • Unit tests
   • Integration tests (if applicable)
   • All checks must pass before proceeding
6. Commit with conventional commit messages

Quality Checks

• Tests exist for all new/changed behaviour
• No new lint warnings or type errors
• Changes are minimal — no unrelated cleanup or feature creep
• Commit messages are descriptive with conventional format
• All delivery layers identified in the plan are addressed

References

• See “Pull Request Process”, “Testing Pyramid”, and “Definition of Done” in .ai/projects/cascadeguard/sdlc.md
• .ai/steering/testing-standards.md
• .ai/steering/git-preferences.md