Back to Home

Challenge 7 – SDD Core (3): Workflow

Complete the following tasks:

1. With “rules” and “skills” in place, how can AI follow software engineering processes for development?

2. Introduction: Workflow

3. Review the following “New Feature Development” workflow:

# Workflow - New Requirement

Complete workflow for new feature development

---

## Step 1: Write specification documents

First, determine the type of feature:
- **New feature**: Create a folder `specs/feature-name/` in the project root
- **Sub-feature of an existing feature**: Update within the existing `specs/feature-name/` folder

### 1.1 Requirement Specification
- Use the `atdd` skill
- Convert requirements into user stories and Gherkin acceptance criteria
- **New feature**: Create `specs/feature-name/req-feature-name.md`
- **Sub-feature**: Insert new user stories and AC into appropriate sections
- **Dependency:** None

### 1.2 Design Specification
- Use the `Fullstack` skill
- Based on requirements, design architecture, APIs, and data models
- **New feature**: Create `design-feature-name.md`
- **Sub-feature**: Update relevant sections
- **Dependency:** Requirement spec must be completed first

### 1.3 UI Design Specification
- Use `Frontend Design`
- Based on requirement + design specs, define layout and interactions
- **New feature**: Create `ui-feature-name.md`
- **Sub-feature**: Update sections
- **Dependency:** Requirement and design specs completed

### 1.4 Consistency Check
Ensure:
- APIs cover all scenarios
- UI covers all user actions
- Data model supports UI
- Naming consistency
- No missing edge cases

### 1.5 User Review
- Manual review by user
- Ensure correctness and usability

---

## Step 2: TDD Development

### 2.1 Principles
- Use `tdd`
- Follow incremental delivery
- Ensure test coverage

### 2.2 Workflow
1. Red – write failing test
2. Green – minimal code to pass
3. Refactor – optimize
4. Commit – after each pass

### 2.3 Git Rules
- Commit after each passing test
- No commit on failure

### 2.4 Docs Sync
- Update specs if needed
- Keep code + docs aligned

---

## Step 3: DoD Validation

### 3.1 Automated Checks
- All tests pass
- Coverage ≥80%
- No lint errors

### 3.2 Manual Testing
- Validate against AC

### 3.3 Completion
- Mark as completed
- Record date and reviewer

---

## Workflow Checkpoints

| Phase | Checkpoint | Output |
|------|-----------|--------|
| Spec | Approved | Docs |
| Dev | Tests pass | Code |
| DoD | Validated | Feature |

---

## Dependencies

Rules:
- Incremental Delivery
- DoD
- test-strategy

Skills:
- atdd
- Fullstack
- Frontend Design
- tdd
- dod
- update-docs

4. Use the workflow to develop a new feature

• Step 1: Ask AI how to execute
• Step 2: Generate a skill
• Step 3: Build feature

5. Challenge: Create a new workflow

• Change Requirement
• Bug fixing
• Testing
• Code Refactoring

6. Load rules, skills & workflows

• Step 1: Download example package
  Download
• Step 2: Customize and load

Back to Home