# Implement

Research, implement, test, document, and review a Fallow feature, fix, refactor, or...

- Repository: https://github.com/fallow-rs/fallow (5289 stars)
- Category: Testing
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add fallow-rs/fallow --skill implement -g -a claude-code -y`
Codex: `npx skills add fallow-rs/fallow --skill implement -g -a codex -y`
Cursor: `npx skills add fallow-rs/fallow --skill implement -g -a cursor -y`
Gemini CLI: `npx skills add fallow-rs/fallow --skill implement -g -a gemini-cli -y`

## Description

Research, implement, test, document, and review a Fallow feature, fix, refactor, or repository improvement. Use when asked to build or change Fallow.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Implement

Deliver the requested change through the native Fallow lifecycle.

1. Read `AGENTS.md`, `docs/README.md`, and
   `docs/development/task-context-map.md`.
2. Inspect the live branch, worktree, open pull requests, and `origin/main`.
3. Write the acceptance criteria and verification plan to the gitignored
   `.plans/<task>.md`.
4. Resolve open decisions before editing. Sort each open question:
   - fact: the code, docs or history hold the answer; look it up;
   - observable: a run shows the answer; probe a fresh build on a public
     fixture with `--format json --quiet`. When the change models another
     tool (pnpm, npm, Bun, tsc), probe that tool too: the oldest supported
     version, the installed one and the latest major. Narrow a version
     boundary down to the patch release;
   - decision: scope, naming, contract or trade-off; ask the maintainer in one
     round, with a recommended answer for each question.
   Record the answers in the plan. Skip this step when no decision is open.
5. For changes with user-facing design decisions, run `panel-review` before
   editing.
6. Create an implementation branch and ready pull request before tracked edits.
7. Implement in pipeline order and keep generated contracts, public docs, and
   companion repositories synchronized. Follow the test evidence rules in
   `docs/development/quality-gates.md`. For a bug, get a command that fails
   before you change code; after a restart, suspect the `.fallow/` cache first.
   Write changelog entries to `changelog.d/<branch>.md`, never to
   `CHANGELOG.md`.
8. Run every applicable gate from `docs/development/quality-gates.md`.
9. Run the reviewer set selected by
   `docs/development/review-routing.md`. Resolve every block.
10. Update the pull request with current verification evidence and the proof
    level of each claim.

The rest: https://github.com/fallow-rs/fallow/blob/HEAD/.agents/skills/implement/SKILL.md