abildtoft/kramme:workflow-artifacts:cleanup

Clean Up Artifacts

Delete workflow artifacts from the current working directory and generated diagram files under ~/.kramme-cc-workflow/diagrams/. This is a destructive command: deletion is recoverable from the system Trash only when trash is installed (see Step 4), so it always confirms first.

Note: For SIW-specific cleanup, consider using /kramme:siw:remove instead. This cleanup command intentionally leaves siw/DISCOVERY_BRIEF.md and siw/SPEC_STRENGTHENING_PLAN.md alone because they can still be active handoff artifacts, while /kramme:siw:remove deletes them as part of destructive SIW cleanup.

Target Files

Targets fall into two groups. Only targets that exist on disk are deleted or reported; missing targets are ignored.

Always candidates for deletion

Visual diagram artifacts (shared across sessions and projects — confirmed separately in Step 3):

• ~/.kramme-cc-workflow/diagrams/*.html (generated by /kramme:visual:* skills)

Review and audit artifacts:

• REVIEW_OVERVIEW.md
• UX_REVIEW_OVERVIEW.md
• PRODUCT_REVIEW_OVERVIEW.md
• PRODUCT_AUDIT_OVERVIEW.md
• PRODUCT_AUDIT.md
• COPY_REVIEW_OVERVIEW.md
• QA_REPORT.md
• QA_BASELINE.json
• AUDIT_IMPLEMENTATION_REPORT.md
• AUDIT_SPEC_REPORT.md
• siw/PRODUCT_AUDIT.md
• siw/AUDIT_IMPLEMENTATION_REPORT.md
• siw/AUDIT_SPEC_REPORT.md

Planning artifacts:

• PR_PLAN_*.md

SIW tracking artifacts (in siw/):

• siw/LOG.md
• siw/OPEN_ISSUES_OVERVIEW.md
• siw/issues/ (directory — candidate only when the SIW marker siw/OPEN_ISSUES_OVERVIEW.md exists; see Step 1)
• siw/qa-intake/ (directory — same condition)

Permanent — deleted only with explicit confirmation (default: kept)

These are durable SIW specifications, not throwaway output. They are kept unless the user explicitly opts in during Step 3.

• siw/FEATURE_SPECIFICATION.md
• siw/PROJECT_PLAN.md
• siw/API_DESIGN.md
• siw/DOCUMENTATION_SPEC.md
• siw/SYSTEM_DESIGN.md
• siw/TUTORIAL_PLAN.md

Workflow

Step 1: Scan

Record which targets exist, as three separate lists: working-directory artifacts, shared diagram files under ~/.kramme-cc-workflow/diagrams/, and permanent specs. Only items discovered here are deleted or reported in later steps, and the siw/OPEN_ISSUES_OVERVIEW.md marker is read here, before anything is deleted.

For the conditional directories:

• siw/issues/ is a candidate only if siw/OPEN_ISSUES_OVERVIEW.md exists. If it contains files that do not match ISSUE-*.md, drop it from the candidates and report it as skipped.
• siw/qa-intake/ is a candidate only if siw/OPEN_ISSUES_OVERVIEW.md exists. If it contains files that do not match QA-INTAKE-*.md, drop it from the candidates and report it as skipped.

If no candidates and no specs exist, report No artifact files found. and stop.

Step 2: Warn on uncommitted changes

If the working directory is a git repository, run git status --porcelain -- against the found working-directory paths. If any found file has uncommitted changes, list them and warn that deletion will discard that work (recoverable from Trash only if trash is installed). Skip this step when not in a git repo.

Step 3: Confirm

Ask the user to confirm before deleting anything. Build the options from the Step 1 lists only — never list files that were not found. Present:

• the always-candidate artifacts found in the working directory,
• the shared diagram files found under ~/.kramme-cc-workflow/diagrams/, noting they are shared across sessions and projects,
• the permanent SIW specs found (default kept; delete only if the user explicitly includes them).

Offer at least: delete artifacts only (keep specs), delete everything found (artifacts + specs), or cancel. Omit the "everything" option when no permanent specs were found. If the user cancels, stop without deleting.

Step 4: Delete

Delete only the confirmed set. Prefer trash for recoverability; use trash -r for directories (siw/issues/, siw/qa-intake/).

If trash is not installed, warn that deletion will be permanent, then fall back to rm / rm -rf:

Warning: 'trash' command not found. Files will be permanently deleted.
Install with `brew install trash` (macOS) or your distro's `trash-cli` package (Linux).

Step 5: Report

• List files and directories that were deleted, and whether they went to the system Trash or were permanently removed.
• List anything skipped (directories with unexpected contents, specs the user chose to keep).
• Note if no artifact files were found.