Software Development Flow Lite
Lightweight version of the full Software Development Flow. Designed for small features requiring 1-5 implementation steps with iterative plan-implement-test-review cycle.
mcp__moira__start({ workflowId: "moira/software-development-flow-lite", parentExecutionId: "none" })Process
Section titled “Process”flowchart LR
A[Study] --> B[Plan] --> C[Approve] --> D[Implement] --> E[Test] --> F[Review] --> G[Commit]
G -->|more steps| D
G -->|done| H[Report]Phases
Section titled “Phases”| Phase | Action | Output |
|---|---|---|
| 1. Project Study | Analyze project structure, codebase, patterns | Project context |
| 2. Task Requirements | Define scope, complexity, acceptance criteria | Task definition |
| 3. Development Plan | Create iterative plan with step-by-step breakdown | Approved plan |
| 4. Implementation Loop | For each step: implement → test → quality check → gate review → commit | Working code |
| 5. Final Report | Summary with evidence and documentation update | Delivered feature |
Features
Section titled “Features”Iterative Implementation
Section titled “Iterative Implementation”Each plan step goes through a validation cycle:
- Implement the step
- Run all tests
- Check code quality (15 standards)
- Gate review by subagent
- Commit with meaningful message
Plan Review
Section titled “Plan Review”Before implementation, a subagent reviewer validates the plan for:
- Completeness of task coverage
- Step granularity and independence
- Consistency with project patterns
Numerical Checks
Section titled “Numerical Checks”Evidence-based validation at each step:
- Test pass count (passed/failed)
- Quality standards met (out of 15)
- Gate review issues (blocking/non-blocking)
When to Use
Section titled “When to Use”- Small features with 1-5 implementation steps
- Bug fixes requiring structured approach
- Quick enhancements with test coverage
- Tasks where full SDF overhead is unnecessary
When to Use Full SDF Instead
Section titled “When to Use Full SDF Instead”- Features with 5+ implementation steps
- Complex multi-component changes
- Tasks requiring extensive project study phases
- Features with significant architectural impact
Example Node Configuration
Section titled “Example Node Configuration”{ "id": "implement-step", "type": "agent-directive", "directive": "Implement current plan step completely and with quality.", "completionCondition": "Step implemented, working functionality created and tested", "connections": { "success": "run-all-tests" }}Related
Section titled “Related”- Software Development Flow — Full development cycle for larger features
- Quick Task — For non-development multi-step tasks
- Workflow Templates Overview — All available templates