reqfile
OPEN SOURCE / BUILT FOR AGENTS

Give your agent
requirements it can check.

Your project's rules, turned into concrete feedback.
Write what must hold. Check it as you code.

Give this to your agent Claude Code · Codex · Cursor

set up https://reqfile.dev/SKILL.md

Then let it connect the dots. Read the skill

Reqfile.yaml
reqfile check
Feedback your agent can act on

One file. Your existing tools. A tighter feedback loop.

FROM INTENT TO FEEDBACK

Make the rules part of the loop.

Requirements live next to your code, so every agent starts with the same expectations.

Reqfile.yaml01 / DEFINE 
# Say what must hold, and why.
reqfile: 1
code:
  - id: EXPLICIT_EXCEPTIONS
    must: No bare except clauses.
    why: Unexpected failures must surface.
    checks:
      - command:
          run: ruff check --select E722 .
          fast: true
          fix_hint: Catch a specific exception.
Agent terminal02 / CHECK → FIX 
$ reqfile check

EXPLICIT_EXCEPTIONS
  E722 Do not use bare `except`
  fix: Catch a specific exception.

# Your agent fixes the code and reruns.
$ reqfile check

1 check run. 0 violations. 0 errors.
Illustrative output
01

Keep the tools you trust.

Run your linters, tests and scripts. Add a decision check when a rule needs judgment.

02

Put context next to code.

Requirements cascade through folders. Your agent can ask what applies before making a change.

03

Close the loop.

Check during edits and in CI. Get the requirement, the finding and a concrete hint for fixing it.

Less guessing.
More feedback.

Set up Reqfile