autofeat docs
Use autofeat

Write a spec

What to put in the pull request body so the agent can finish the turn.

Open a draft pull request and put the spec in its body. A short title is not a spec. With implementation enabled in your settings and autofeat:go on the pull request, request @Autofeat implement. Autofeat creates draft children for the accepted tasks. Each child needs checks and an independent review; you decide whether to merge it. The root stays draft by default.

Use the headings below so the planner can identify the scope and requirements.

Goal

One or two sentences. Name the behaviour the user should see when the pull request merges. Name the repository paths only when the goal is a specific file.

Acceptance criteria

A list the agent can check. Each line is a fact that is true or false. Prefer commands and observable output over adjectives.

  • just check passes.
  • GET /health returns 200 when the worker heartbeat is fresh.
  • The new flag --explain prints one row per guard.

Constraints

Rules the agent must not break. Examples: do not add a dependency, do not change the public config schema, keep functions at or under 50 lines, ASCII only in user-facing copy.

Out of scope

Name the work you do not want in this pull request. Agents fill silence with extra edits. Out of scope is how you stop that.

Affected surfaces

List repository path prefixes where changes are allowed. Task paths must stay inside the declared surfaces.

References

List repository file paths with useful existing code or tests. References must be typed paths, not URLs. Cross-repository and issue references require explicit policy permission. Do not paste the whole tree.

Template

Copy this into the pull request body and replace the placeholders.

## Goal

<one sentence: what is true after merge>

## Acceptance criteria

- <checkable fact>
- <checkable fact>

## Constraints

- <rule the agent must not break>

## Out of scope

- <work that belongs in another pull request>

## Affected surfaces

- <allowed directory/>

## References

- <existing code path>
- <existing test path>

What the agent cannot change

Policy comes from .autofeat/config.yml on the default branch. Editing that file on the pull request branch does not change the run. Budgets, allowed agents, and merge mode stay at the default-branch snapshot (policy_sha on the sticky comment).

Labels are the control surface for this pull request. See Labels.

On this page