FedDIY/docs/WORKFLOW.md

Development Workflow

This project uses Red-Green TDD/BDD and feature-branch workflow with pull request review.

Red-Green TDD/BDD Cycle

For each behavior increment:

1. Red: describe behavior with a failing specification/test.
2. Green: implement the smallest change needed to satisfy behavior.
3. Refactor: improve structure while keeping behavior unchanged.

BDD intent:

• Express behavior in user-meaningful terms.
• Prefer scenario-oriented acceptance criteria before implementation details.
• Keep unit and integration tests aligned with documented behavior.

Definition of done for a change:

• Behavior is specified and verified.
• Relevant tests are passing.
• Refactoring has preserved behavior.
• Documentation is updated when contracts or workflows change.

Feature-Branch Workflow

Use short-lived branches from main.

Branch pattern examples:

• feature/
• fix/
• docs/
• chore/

Branch workflow:

1. Create branch from latest main.
2. Commit small, reviewable increments.
3. Open pull request early.
4. Keep branch current with main.
5. Merge after review and checks pass.
6. Delete merged branch.

Pull Request Expectations

• Clear behavior statement and acceptance criteria.
• Test evidence for the behavior change.
• Notes on any architectural or moderation impact.
• Scope limited to one cohesive change.

Agent Collaboration Rules

• Agents may support test planning, scenario writing, and review checklists.
• Agents must not generate executable core project code.
• For implementation guidance, agents should link primary sources and provide paraphrased walkthroughs.