From story to deploy

This is how a task runs at AWL when Claude Code works alongside you. The steps are not a rule for every small thing – a typo does not need seven stations. For anything the size of a story, the order holds.

1. Story
2. Understand
3. Build
4. Test
5. Review
6. Ship
7. Learn

Shape the story

Code only starts once it is clear what done means. clickup-stories creates user stories with acceptance criteria in ClickUp and keeps them up to date.

Tell ClaudeCopy

Write a user story for password reset by email in the list “Sprint 12”.

Understand

Depending on where you start:

• Something is broken → analyse-bug reproduces the error, narrows down the cause and delivers a structured diagnosis. Only then does anything get fixed.
• New or upgraded dependency → research pulls the official docs before Claude uses an outdated API from memory.
• Unfamiliar codebase → explain-codebase for a fast way in.

BugCopy

The upload fails for files over 10 MB – not working since the last release.

Build

This is where the stack plugins work. They know the AWL templates and internal packages:

• Android and Kotlin Multiplatform: kotlin-expert
• iOS and SwiftUI: swiftui-expert-skill
• SvelteKit and Payload: awl-npm-packages – check first what @awl/* already solves
• Wiring a new or existing SvelteKit app with the @awl/* packages: sveltekit-app-setup
• Extending a Payload backend with the @awl/payload-* packages: payload-plugins
• UI components with AWL tokens: component-gen

For big tasks across many files, orchestrator splits the work across parallel subagents.

Test

The agent Tester writes tests in the style of each stack, using testing-web, testing-swift, testing-android and testing-dotnet.

Tell ClaudeCopy

@awl-testing:Tester write tests for the new PasswordResetService.

Review

Before every merge request:

• review looks for bugs, security issues and known failure patterns.
• ac-checker checks every acceptance criterion of the story against the code.
• design-review finds hard-coded colours and spacing where design tokens belong.

Tell ClaudeCopy

Review my changes, then check the ACs.

Ship

gitlab-cicd sets up the pipeline from the AWL components, deploying-to-kubernetes the deploy job. Before a deploy change is merged, pre-deploy-check runs – it checks CI variables, protected branches and DEPLOYMENT_VALUES against the real GitLab state, before ArgoCD turns red.

Tell ClaudeCopy

Can I merge this? Run the pre-deploy check.

The playbook Deploy a web app shows the whole path.

Learn

At the end of a session, reflect records what Claude should know next time – as a rule in CLAUDE.md or in memory.

Tell ClaudeCopy

/awl-general:reflect