Reverse engineer clean behavioral specs from any codebase by analyzing source, binaries, docs, git history, and tests, then sanitizing outputs to strip implementation details while preserving provenance metadata.
Generic Analyzer agent. Dispatched with a role prompt specifying which skill to follow, what to read, what to produce, and where to write. Loads all analysis skills.
Generic sanitizer worker agent. Reads raw specs and rewrites them as clean behavioral specs. Loads sanitization and provenance skills.
Reverse engineer clean behavioral specs from any codebase.
Greenfield reads source code, documentation, SDKs, runtime behavior, and binaries, then produces behavioral specifications, test vectors, acceptance criteria, and a full provenance trail. The output describes what the software does — not how any particular codebase does it — so a fresh implementation team can build against the specs without inheriting the original's internal structure.
Greenfield is a Claude Code plugin. It runs inside the claude CLI and uses Claude agents as the workers that read code, write specs, and audit output.
/plugin marketplace add prime-radiant-inc/prime-radiant-marketplace
/plugin install greenfield@prime-radiant-marketplace
Restart Claude Code after installing.
claude
> /analyze /path/to/target
/analyze runs a seven-layer pipeline. It discovers the available intelligence sources (source, docs, SDK, community, runtime, binary, git history, tests, UI, contracts), gathers evidence from each, synthesizes behavioral specs with provenance citations, generates test vectors and acceptance criteria, sanitizes the specs of implementation details, then runs a second-pass review of the result.
Target shape doesn't matter. Greenfield has been used on single-file minified JavaScript bundles and on source-tree projects; the pipeline also has a path for decompiled native binaries. The methodology adapts to what's there.
Workspace output:
workspace/
├── raw/ # Analysis artifacts with source references
├── output/ # Sanitized specs for the implementation team
│ ├── specs/
│ ├── test-vectors/
│ └── validation/
└── provenance/ # Citation audit trail
claude
> /sanitize /path/to/workspace
Re-runs the sanitization pass on an existing workspace. Useful when the initial pass left contamination that the audit caught.
Greenfield stops at the specs. The implementation team reads workspace/output/ and builds against the behavioral specs, test vectors, and acceptance criteria there.
The pipeline dispatches agents with role-specific prompts across the seven layers. Each dispatch runs one of two generic agent types loaded with a specific skill:
discovery-agent, bundle-splitter, chunk-analyzer, function-analyzer, doc-researcher, community-analyst, sdk-analyzer, cli-explorer, behavior-observer, feature-discoverer, architecture-analyst, api-extractor, synthesizer, module-mapper, deep-dive-analyzer, behavior-documenter, user-journey-analyzer, contract-extractor, spec-verifier, source-completeness-checker, test-vector-generator, test-generator, acceptance-criteria-writer, spec-reviewer, structural-leakage-reviewer, content-contamination-reviewer, behavioral-completeness-reviewer, deep-read-auditor, fidelity-validator.| Layer | Roles | Output |
|---|---|---|
| L1: Intelligence | bundle-splitter, chunk-analyzer, function-analyzer, doc-researcher, community-analyst, sdk-analyzer, cli-explorer, behavior-observer | Raw evidence from source, docs, SDK, community, runtime, binary |
| L2: Synthesis | feature-discoverer, architecture-analyst, api-extractor, synthesizer, module-mapper | Feature inventory, architecture model, module map |
| L3: Deep Docs | deep-dive-analyzer, behavior-documenter, user-journey-analyzer, contract-extractor | Behavioral specs, journeys, contracts |
| Gate 1 | spec-verifier | Correctness, contradictions, gaps |
| Gate 1b | source-completeness-checker | Every user-facing surface captured |
| L4: Validation | test-vector-generator, test-generator, acceptance-criteria-writer | Test vectors, test specs, acceptance criteria |
| Gate 2 | spec-reviewer | Implementation leakage, completeness, quality |
| L5: Sanitization | sanitizer | Output specs rewritten from understanding, not copied |
| L6: Review | structural, content, completeness reviewers + deep-read auditors | Second-pass contamination review |
| L7: Fidelity | fidelity-validators | Flags behavioral detail lost or weakened during sanitization |
Apache 2.0. Copyright 2026 Prime Radiant, Inc.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub prime-radiant-inc/prime-radiant-marketplace --plugin greenfieldAn iterative implementation methodology that pairs with superpowers. Extracts requirements with proof obligations from large spec collateral, defines a walking skeleton that closes a real journey, then loops through audited sprints building a behavior evidence corpus until an auditor confirms the product matches the spec. Designed for comprehensive or ambiguous specs where the upfront writing-plans flow loses the plot.
Streamlined Linear integration - one tool, seven actions, zero bloat
Two skills for adversarial code review. parallel-adversarial-review dispatches two same-model reviewer subagents in parallel under a competitive scoring frame, aggregating findings and taking the worst severity on disagreement. multi-model-adversarial-review extends this to N installed coding-agent CLIs (claude, codex, gemini, opencode, amp, aider) with a cross-critique stage that catches hallucinations and severity inflation, then synthesizes a deduplicated report. Includes a fixture-based eval suite that scores precision and recall against planted defects.
A documentation department in a box: studies a project and its readers, decides the doc portfolio with you, writes contributor/user/adopter docs with verified claims, and keeps them true as the code moves
Records Claude Code sessions as agent trajectories in cxdb
Reverse engineering service functionality from source code
GitHub Spec-Kit integration for Specification-Driven Development - define WHAT and HOW before coding
Specification-Driven Development with Process Discipline for Claude Code
Spec-driven development with search, conflict detection, and reporting
Spec-driven development plugin for Claude Code. Markdown specs as the source of truth, code downstream.
Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns