improve

Score repository targets against rubrics and execute isolated improvement loops.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mferris77/SpringBoard --skill improve-mferris77
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: improve
Source: https://github.com/mferris77/SpringBoard/tree/main/vscode-citadel-harness/skills/improve
Command: npx skills add https://github.com/mferris77/SpringBoard --skill improve-mferris77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

/improve automates the discovery, prioritization, and remediation of quality issues across a product repository by scoring against a human-authored rubric and executing targeted improvements until progress plateaus. It removes manual iteration overhead by orchestrating programmatic checks, structural analysis, perceptual evaluators, isolated experiments, and verification steps in a repeatable loop. The Skill enforces human approval for rubric changes and strong regression gates to protect security and stability.

Core Features & Use Cases

  • Autonomous Scoring: Runs programmatic, structural, and perceptual evaluations (three evaluators) to produce an objective scorecard per axis.
  • Single-Axis Selection & Attack: Selects the highest-leverage axis using a transparent formula, executes isolated experiments or direct edits, and archives approach comparisons.
  • Verification & Safety Gates: Performs programmatic, structural, perceptual, and behavioral simulation verifications; aborts and reverts on regressions or failing security checks.
  • Campaign Mode & Level-Up: Supports multi-loop campaigns with resumable state files, level-up snapshots, and human approval workflows for rubric re-anchoring.
  • Use Case: Use it to iteratively raise onboarding, documentation accuracy, security posture, or demo effectiveness for a codebase or product.

Quick Start

Invoke the Skill with a target rubric slug, for example: /improve citadel --n=3 to run three improvement loops against the citadel target.

Frequently Asked Questions about improve

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate quality improvement for my codebase against a custom rubric?▼

Automated quality improvement scores a repository target against a human-authored rubric, selects a high-leverage axis, executes an isolated improvement, and verifies results. It runs programmatic checks, structural analysis, and perceptual evaluators in a repeatable loop until progress plateaus.

How do I run isolated improvement experiments without breaking my main repository branch?▼

Isolated improvement experiments use worktree-based branches to execute targeted attacks on a single quality axis. This ensures changes are contained, verified against programmatic and structural checks, and automatically reverted if regressions or security failures occur.

Can I continuously raise product quality across multiple loops with campaign state?▼

Campaign mode raises product quality across multiple loops using resumable state files. It supports campaign continuation, level-up snapshots, and human approval workflows for rubric re-anchoring when progress plateaus.

What is the best way to prioritize quality remediation across a product repository?▼

Prioritizing quality remediation uses a transparent formula to select the single highest-leverage axis from an objective scorecard. It evaluates programmatic, structural, and perceptual metrics to target the most impactful improvement rather than addressing issues manually.

How does behavioral simulation verify user-facing quality improvements?▼

Behavioral simulation verifies user-facing quality improvements by testing how changes affect user-facing axes. It acts as a safety gate alongside programmatic, structural, and perceptual verifications to abort and revert any changes that introduce regressions.

Do I need to manually review rubric changes during an automated quality campaign?▼

Automated quality campaigns require human approval for rubric changes to ensure re-anchoring remains safe. The system enforces this workflow alongside strong regression guards to protect repository security and stability during autonomous loops.