Module Workflow
The 7-phase development lifecycle for CleanFramework.Module projects.
Invocation
/module-workflow
Phases
| Phase | Agent | Description |
|---|---|---|
| 1. Feature Planning | Feature Planner | Requirements analysis, user stories, acceptance criteria |
| 2. Architecture Design | Software Architect | Layer design, task list, vertical slices |
| 3. Implement | Backend Developer | Layer-by-layer implementation (Shared → Domain → Application → Infrastructure) |
| 4. Test | Tester | Unit tests (Domain) and integration tests (Application) |
| 5. Document | Technical + Business Doc Writers | API docs, XML comments, user-facing docs |
| 6. Review | Software Architect | Architectural compliance, quality gates |
| 7. Deliver | Software Architect | Final checks, PR creation |
Quality Gates
All must pass before a PR is opened:
dotnet build --configuration Release— zero warningsdotnet test --configuration Release— all tests pass- Layer dependency rules followed
- Handler isolation rule followed
- EF Core entities have explicit
IEntityTypeConfiguration<T> - XML doc comments on all public types
- Shared constraint constants used (no magic numbers)
- GDPR handlers present if module stores PII