Skip to content

Consider splitting harden: substantive-deliverable audit vs thin-slice spec/plan audit #16

@mickeylorenzini

Description

@mickeylorenzini

Type: meta-tooling | Status: needs-more-context | Scope: session-sized

Problem

The harden skill currently spans both YAGNI-approved substantive deliverables (research artifacts, grant sections, strategy docs) and YAGNI-violating-large spec/implementation plans. With the user's recent shift toward minimal spec/plan docs, applying the full harden cycle (web research + dual-pass audit + multi-iteration fix) to small spec/plan artifacts is increasingly disproportionate to the artifact size.

Source of truth for harden is this repo (mickeylorenzini/harden); dotclaude consumes a copy at skills/harden/. Any split happens upstream here first.

Proposed approach

Investigate splitting harden into two skills: (a) the existing harden retained for substantive deliverables (full cycle), (b) a new lightweight skill (working name TBD) for thin-slice spec/plan compliance check (single pass, structural-only, no web research). Defer until more in-flight friction with current single-skill harden is observed; this is a refinement, not an emergency.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions