regrind.dev

A LITTLE STRUCTURE. A LOT OF POSSIBILITY.

Give your agent
a way to ship.

Turn a rough request into reviewed work.
A repeatable development process that lives in your repo.

Start with setup

Your agent does the work. You set the standard.

BUILT FOR YOUR TOOLS
Claude Code Codex Cursor
03 / COOKWORKFLOW PREVIEW
IN3 approved work items
OUTImplementation + check results
The millerFeeds the task and turns the mill’s crank.
FOLLOW ONE TASK / ADD DARK MODEILLUSTRATIVE WORKFLOW

/grind-cookPLANNED

Work it. Refine it.

The approved pieces pass through the mill. Rough input becomes implementation, one slice at a time.

WHAT YOU GETCode with a reason behind it.
  • Implement tokens
  • Wire the toggle
  • Exercise the behavior

The preview illustrates the workflow. It runs no agent commands.

Choose a phase, or run the whole loop.

Early development. Setup, Plan and Ship are available from a local checkout. Triage, Cook, QA and Review are on the roadmap. What can I use today? ↗

01 / A PROCESS YOU CAN FOLLOW

Move the work forward.
Keep the decisions visible.

The same task moves through the loop.
Each step leaves something you can inspect.

TRIAGE → PLAN

Choose the right work.

Clarify the request, keep duplicates out of the queue, and agree on the scope. A cross-reviewed plan gives the agent something concrete to implement.

REQUEST→APPROVED PLAN
COOK → SHIP

Refine it into a change.

Work through the approved scope, run the project checks, and prepare a PR with a summary and QA plan. Today, /grind-ship includes the implementation step.

IMPLEMENTATION→REVIEWABLE PR
QA → REVIEW

Prove it. Make the call.

Check the behavior against the plan. Send failed work back for a fix. Review the code and evidence together; merging and deploying stay with a person.

QA EVIDENCE→HUMAN DECISION
02 / AT HOME IN YOUR REPOSITORY

A little structure.
Right beside your code.

Regrind installs plain-text skills and a project profile. Your coding agent picks them up in the tools you already use.

Your conventions.
Commands, evidence, reviewers, and what counts as done.
Your tools.
Skill copies for Claude Code, Codex, and Cursor.
Your rules.
The profile stays yours. Updates preserve your edits and text outside the managed rules block.
your-repo /VERSIONED WITH YOUR WORK
├─ .grind/
├─ profile.md your project’s working agreement
└─ manifest.json installed files and versions
├─ AGENTS.md managed Regrind rules block
├─ .claude/skills/grind-*
├─ .agents/skills/grind-*
└─ .cursor/skills/grind-*
.GRIND/PROFILE.MD

Project commandstest · lint · build

Acceptancewhat counts as done

Evidencewhat reviewers can verify

03 / START WITH YOUR REPO

One setup.
A shared way to work.

Regrind currently installs from a local checkout.
Node 20+. No npm release yet.

  1. 01

    Install into your project.

    Point the installer at your repository. It copies the skills for each coding tool and creates the project profile.

  2. 02

    Teach it your conventions.

    Open the project in your coding tool and run /grind-setup. Review the profile and fill in what the repository cannot tell it.

  3. 03

    Plan a real task.

    Use /grind-plan, review the plan, and approve it. Then /grind-ship works toward a PR. You keep the final decision.

LOCAL CHECKOUT REQUIREDAVAILABLE TODAY
1 / INSTALL 
node /path/to/regrind/bin/grind.js install --target /path/to/your-repo

Replace both paths with your local directories.

2 / IN YOUR CODING TOOL/grind-setup/grind-plan "Add dark mode"

Git and GitHub CLI are needed by the shipping workflow. Cross-review requires another configured coding harness. Installation does not merge or deploy anything.

No checkout yet? Follow development at rebranch ↗
AVAILABLE TODAY

Installer · Setup · Plan · Ship

ON THE ROADMAP

Triage · Cook · QA · Review

BUILT BY REBRANCH / MADE TO ITERATE

One more
good loop.

Start with your repo Explore the motion studies ↗