One-click install
npx skills add https://github.com/swingerman/disciplined-agentic-engineering --skill refine-swingerman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refine
Source: https://github.com/swingerman/disciplined-agentic-engineering/tree/main/engineer/skills/refine
Command: npx skills add https://github.com/swingerman/disciplined-agentic-engineering --skill refine-swingerman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

refine helps engineers safely clean up already-working feature code by removing churn while protecting the behavior contract defined by ACs and specs.

Core Features & Use Cases

  • Charter-bound refactoring proposals: Rejects refactor ideas that violate CHARTER.md, ensuring contract consistency instead of “just make it nicer.”
  • Graceful breaking-change handling: Classifies proposed breaking changes as consumer-facing (with deprecation/migration paths) versus internal-only (hard changes allowed).
  • Deterministic, independent checkpoint workflow: Uses explicit handoff gating, branch hygiene checks, progress breadcrumbing, and parallel review subagents with optional duplication scanning.

Quick Start

Run the engineer refine workflow after your feature code is implemented and passing tests to clean up changed code while keeping acceptance behavior stable.

Frequently Asked Questions about refine

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

FAQPage Schema
How do I refactor feature code without breaking acceptance tests?

Charter-bound refactoring preserves your feature's behavior contract by filtering cleanup proposals through CHARTER.md, ensuring naming and structure improvements do not alter passing acceptance test specs.

What is the best way to clean up passing code before running a quality analyzer?

Run a charter-validated refinement workflow at your checkpoint after tests pass and before quality analysis, dispatching parallel reviews for reuse and efficiency while applying only human-selected safe edits.

How do I handle breaking changes during a code refactor?

Graceful breaking-change handling classifies proposed refactors as consumer-facing, requiring deprecation or migration paths, versus internal-only, where hard changes are allowed without external impact.

Can I run parallel code reviews for duplication and efficiency on my feature branch?

Parallel review subagents dispatch independent reuse, quality, and efficiency checks with optional deterministic duplication scanning, gated by explicit branch hygiene and handoff checks before edits apply.

When should I avoid charter-bound refactoring on my codebase?

Avoid this refactoring approach when your feature code lacks passing acceptance tests, as the workflow requires green specs at checkpoint 6 to enforce its deterministic behavior contract guardrails.

Does the refine workflow require specific branch hygiene checks before refactoring?

Yes, deterministic entry gates enforce branch hygiene and handoff validation via dedicated scripts, ensuring your codebase meets explicit progress breadcrumbs before dispatching any review subagents.