Skip to main content
Yellowhammer coordinates local tools to turn product intent into reviewable work. These concepts explain what belongs to a Project, how a Night progresses, and what the recorded evidence can tell you.

Projects, Features, and Work Cards

Understand product scope, one in-flight Feature, and repository-scoped work in Linear.

The lifecycle of a Night

Follow author, build, and land Acts through local execution and reporting.

Verification and Definition of Done

Read clause-level evidence and distinguish unmet, unresolved, and unchecked criteria.

Local execution and credentials

Understand local orchestration, external services, and permission boundaries.

​
The core objects

A Project groups one product’s repositories, specification source, Linear project, and configuration. A Feature describes an intended outcome. Its Work Cards carry the repository-scoped pieces of work. A Night is a scheduled window of activity for a Project. One Feature is in flight at a time, but several can land sequentially during the same Night. Landed Features can remain in the unmerged stack while you review their pull requests.
Planned relationship diagram
Yellowhammer core objects

Show how Projects, Nights, Features, Work Cards, and Night Summaries relate.

Planned diagram: one Project scopes a Night and Feature; Work Cards and a Night Summary carry its work and result.

​
Read evidence at the right level

Use a Work Card’s Attempts, review Rounds, and Checks to investigate an individual piece of work. Use the Feature’s Definition of Done and Verification report to evaluate the intended outcome across repositories. Use the Night Summary for what happened during that Night, including failures and decisions still waiting. Yellowhammer coordinates agents and records their results. You make triage decisions in Linear and merge decisions in GitHub.

​
Next steps

Projects, Features, and Work Cards · Review the morning