Docs
Issues and Projects
GitHub Issues record both work and decisions. The project board shows how that work moves.
Before starting
Section titled “Before starting”- Introduce yourself in Discussion #76.
- Search open and closed issues.
- Choose an issue marked
Ready, or open a scoped issue for triage. - State objective, acceptance evidence, public interface, assumptions, refusal conditions, and downstream consumers.
- Work on a branch and open a pull request; never commit directly to
main.
When posting a substantive issue update, mention the original issue author so they receive the context they asked for.
Labels and status
Section titled “Labels and status”Every issue carries type:*, P*:, skill:*, and priority:* labels. Priority follows the
dependency graph. Ready means fully specified and unblocked. needs-human-decision means an
agent must present the choice and stop. wants-expert-review means implementation can proceed but
the pull request must name what an expert should evaluate.
Read the complete board conventions and contribution guide.