From something you want to a pull request you can merge.
Intentions and deliverables
An intention records why a change matters and the full list of deliverables needed to call it done. Deliverables are editable markdown descriptions of expected behavior. They can stay concise while the team learns what it is building.
The branch groups a selected set of deliverables. It becomes a pull request when one is opened. The group is a handoff and review boundary; it does not own a second set of requirements.
The brief
Copy the agreed intention and selected deliverables into your coding agent or normal development process. A brief supplies purpose and scope without requiring a separate implementation planning pass.
Review and delivery
The PR review compares the selected promises with code at the reviewed head and base. The app and GitHub use the same stored assessment, findings and score. A changed head or accepted promise makes old evidence stale.
Intention status combines its deliverables across PRs. A merged PR with missing behavior remains unfinished. A source-reviewed deliverable in a merged PR is delivered in code; runtime verification and live deployment are separate facts.
Stories remain the accepted product promises. Review observations can reveal regressions or incomplete coverage, but do not silently rewrite those promises to match the implementation.
Markdown source
# Getting work done
From something you want to a pull request you can merge.
MCP use: Use this page when someone wants to know how work flows through Foreloop, from a request to a merged change.
Related routes:
- `/intentions`
- `/tasks`
## Intentions and deliverables
An intention records why a change matters and the full list of deliverables needed to call it done. Deliverables are editable markdown descriptions of expected behavior. They can stay concise while the team learns what it is building.
The branch groups a selected set of deliverables. It becomes a pull request when one is opened. The group is a handoff and review boundary; it does not own a second set of requirements.
## The brief
Copy the agreed intention and selected deliverables into your coding agent or normal development process. A brief supplies purpose and scope without requiring a separate implementation planning pass.
## Review and delivery
The PR review compares the selected promises with code at the reviewed head and base. The app and GitHub use the same stored assessment, findings and score. A changed head or accepted promise makes old evidence stale.
Intention status combines its deliverables across PRs. A merged PR with missing behavior remains unfinished. A source-reviewed deliverable in a merged PR is delivered in code; runtime verification and live deployment are separate facts.
Stories remain the accepted product promises. Review observations can reveal regressions or incomplete coverage, but do not silently rewrite those promises to match the implementation.