pickfit

BrowseDeveloper CLIs

scafld

Deterministic protocol that hardens specs, governs phased builds, and gates completion with adversarial review.

Tested on Linux

Use it

Linux x86_64

  1. pipx install scafld (ranked candidate 1)

    pipx install scafld

Check that it works

scafld --version 2>&1

The output should contain “2.5.10”.

First thing to try

mkdir -p /tmp/scafld-demo && cd /tmp/scafld-demo && scafld init 2>&1
cd /tmp/scafld-demo && scafld plan add-cache 2>&1

In your project folder, run scafld init to set it up, then create a spec with scafld plan <name>.

What it does

  • Create draft specs in Markdown
    How to use it
    1. In your project folder, run scafld init.
    2. Run scafld plan <name> to create a draft spec.
    3. Open the new file in .scafld/specs/drafts/<name>.md to edit it.
    Tested
  • Stress-test draft specs before you approve them
    Not shown working
  • Run the adversarial review gate
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 1 of 3 features work
  4. Works offline

Good for

  • question the plan before the code
  • run the adversarial review gate
  • sign an ed25519 receipt on clean pass
  • re-check signed receipt in CI
  • summarize session-derived quality metrics

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 2.5.10

Differences the test machine hit

  • README: Quick Start runs `scafld approve add-cache` with no git setup or reason
    In the test: git init plus an initial commit and `scafld approve add-cache --reason ...` to override in-progress harden round
  • README: `scafld review add-cache --print-context` renders the review brief
    In the test: task must be advanced through approve/build with passing acceptance to status review before `scafld review --print-context` works; on draft/active it exits 4

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.