Trim verbose planning documents while preserving API references and decision data.
npx skills add https://github.com/dcosson/h2 --skill plan-tighten
Please help me install this Agent Skill. Skill: plan-tighten Source: https://github.com/dcosson/h2/tree/main/internal/config/templates/styles/opinionated/skills/plan-tighten Command: npx skills add https://github.com/dcosson/h2 --skill plan-tighten
Plan Tighten surgically trims verbosity and restated rationale from planning docs without losing fidelity, removing review residue, duplicated sections, and unnecessary prose to keep the plan concise and auditable.
Apply plan-tighten to a target plan document (docs/plans/your-plan.md) to generate a tightened, audit-ready version.
High-intent search queries and answers about installing and using this skill.
Trim verbose planning documents by applying a tightening workflow that removes restated rationale and duplicate sections while preserving API/interface signatures, acceptance criteria, and migration steps. This produces a lean, auditable plan ready for final approval.
Removing duplicate sections from engineering plan docs requires phase-preserving cuts that eliminate review residue and extraneous prose while retaining essential decision data. A baseline plan and its associated review history compute diffs to identify redundant content safely.
Tightening project plans after multiple review rounds is the core use case. The process strips review residue and duplicated explanations while keeping migration ordering, audit tables, and essential impact analysis intact for a concise, auditable final version.
Diff-based plan rewriting preserves acceptance criteria by enforcing mandatory retention of API/interface signatures, URP/EO/AA commitments, and migration order steps during phase-preserving cuts. It computes differences against a baseline plan and review history to remove only extraneous prose.
Auditing planning docs before final approval requires a baseline plan document and its associated review history. These inputs compute diffs to identify review residue, duplicate sections, and restated rationale for removal while maintaining essential decision data and audit tables.
Avoid automated plan tightening on product plans lacking a baseline document or associated review history, as diffs cannot be computed without them. The process requires these inputs to safely perform phase-preserving cuts without losing essential decision data and migration ordering.
skogaiIdentify unnecessary complexity and speculative abstractions in codebase diffs.
cogni-workValidate and package Deliver-phase artifacts into an executive-ready export.
truongnatRecord durable lessons and decisions during software development workflows.
EndUser123Compress Python source files and documentation to token-efficient outputs.
