Skip to content
Back to skills

Compaction

ASecurity

Compress phase outcomes into a dense, structured handoff brief that preserves decisions, risks, and next-step context without carrying the entire history forward.

  • 207 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 4, 2026
businessgo

Security analysis

A100/100

Pro scans all 13 files and shows the line behind each finding

Scanned September 4, 2026

npx -y skills add NeverSight/skills_feed --skill compaction --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Compaction?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Compaction
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/neversight-compaction/badge)](https://www.skillsdirectory.com/skills/neversight-compaction)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: compaction
description: Compress phase outcomes into a dense, structured handoff brief that preserves decisions, risks, and next-step context without carrying the entire history forward.
---

# Compaction

Use this skill when a coordinator or support capability needs to condense a phase boundary into a smaller, structured brief for downstream phases or future iterations.

## Goals
- Preserve the concrete decisions and outcomes from a completed phase.
- Reduce context size without losing the important reasoning trail.
- Produce a compact handoff that downstream work can consume quickly.

## Required Inputs
- The completed phase artifact or artifacts
- The current workflow phase and next intended phase
- Relevant memory entries for the phase boundary
- Any open questions, risks, or unresolved constraints

## Required Outputs
- A dense structured brief for downstream use
- A list of preserved decisions and outcomes
- A list of remaining risks or follow-ups

## Procedure
1. Extract the concrete outcomes from the completed work.
2. Keep only the decisions, constraints, and evidence that matter for downstream work.
3. Separate verified facts from remaining uncertainty.
4. Record follow-up needs clearly and briefly.
5. Return a compact brief that can replace rereading the full history.

## Quality Bar
- The brief must be shorter than the source material.
- The brief must preserve the next-step context needed by downstream phases.
- The brief must not introduce new design or implementation decisions.

Files in this skill

  • SKILL.md1.5 KB
  • description_ar.txt236 B
  • description_cn.txt136 B
  • description_de.txt208 B
  • description_en.txt163 B
  • description_es.txt191 B
  • description_fr.txt212 B
  • description_it.txt194 B
  • description_ja.txt202 B
  • description_ko.txt191 B
  • description_ru.txt309 B
  • description_tw.txt136 B
  • stats.json68 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…