Contributing

Reporting Issues

Found a bug or have a feature request? Open an issue on the relevant GitHub repository:

• Unbound Force Website — this website
• Gaze — test quality analysis tool
• Unbound Force — agent personas and roles

Include steps to reproduce, expected behavior, and actual behavior. For feature requests, describe the problem you are trying to solve.

Submitting Pull Requests

We follow the standard GitHub pull request workflow:

1. Fork the repository
2. Create a feature branch named with a number prefix (e.g., 003-feature-name)
3. Make your changes
4. Submit a pull request against the main branch
5. Address any review feedback from The Divisor council

All pull requests are reviewed by The Divisor — a council of three sub-personas (The Guard, The Architect, and The Adversary) that evaluate intent, structure, and resilience. Collective approval from all three is required before merge.

Conventional Commits

All commit messages must follow the Conventional Commits format:

type: description

Valid types:

The Speckit Workflow

All non-trivial feature work goes through the Specify pipeline. This ensures structured planning before implementation:

constitution -> specify -> clarify -> plan -> tasks -> analyze -> checklist -> implement

Each stage builds on the previous one:

• Constitution — project-level governance and principles
• Specify — turn a feature description into a structured specification
• Clarify — reduce ambiguity before planning
• Plan — generate the technical implementation plan
• Tasks — create actionable, dependency-ordered task list
• Analyze — cross-artifact consistency check
• Checklist — requirement quality validation
• Implement — execute the plan task by task

The constitution (.specify/memory/constitution.md) is the highest-authority document in any Unbound Force project. All work must align with it.

Links

• Unbound Force GitHub Organization
• Website Repository
• Gaze Repository
• Specify (spec-kit)