Spec Loop Compact Task File
- 45 installs
- 34 repo stars
- Updated July 27, 2026
- dpolivaev/spec-loop
Compacts a Spec Loop task file, trimming and consolidating an evolving spec/task document so it stays small and focused as work progresses.
About
A Spec Loop skill that compacts a task file, consolidating and trimming an evolving spec document so it stays small, current, and focused on the next increment of work. It supports the design-first Spec Loop discipline of keeping each spec local and releasable rather than letting task files bloat over time. A solo builder reaches for it mid-workflow when a task file has grown noisy and needs to be tightened before continuing.
- Compacts and consolidates the task file
- Keeps specs small and local to the next step
- Part of the Spec Loop design-first framework
- Maintains traceable Markdown/AsciiDoc task files
Spec Loop Compact Task File by the numbers
- 45 all-time installs (skills.sh)
- Ranked #837 of 1,879 Documentation skills by installs in the Skillselion catalog
- Data as of Jul 29, 2026 (Skillselion catalog sync)
npx skills add https://github.com/dpolivaev/spec-loop --skill spec-loop-compact-task-fileAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 45 |
|---|---|
| repo stars | ★ 34 |
| Last updated | July 27, 2026 |
| Repository | dpolivaev/spec-loop ↗ |
What it does
Compacts a Spec Loop task file, trimming and consolidating an evolving spec/task document so it stays small and focused as work progresses.
Who is it for?
Solo devs whose Spec Loop task file has grown large and needs consolidating.
Skip if: Anyone not using the Spec Loop task-file format.
When should I use this skill?
A task file has accumulated noise and should be trimmed before further work.
What you get
A tight, current task file scoped to the next increment of work.
- a compacted task file
Files
Task-file path only.
Source of truth
Use the active task file as the source of truth.
Before compacting, re-read the current subtask and the task-level sections and diagrams it depends on.
Rules
Compaction must preserve meaning exactly.
It may move, rewrite, or reorganize section content to remove duplication and shrink the active task file, but it must preserve:
- decisions;
- dependencies;
- constraints;
- review-relevant facts; and
- implementation and test expectations.
Keep shared context at task level. Keep one authoritative location for each piece of section content. Keep brief references or restatements only when remaining work still needs them to understand the current subtask safely.
Allowed changes
- Move subtask-specific Research, Design, and Test specification into
the relevant subtask.
- Rewrite duplicated section content into a shorter equivalent form.
- Reorganize section content to remove duplication and make the
active task file smaller.
- Compact duplicated section content instead of repeating it.
Forbidden changes
Do not use this skill to:
- make new design decisions;
- narrow or expand scope;
- remove still-needed detail; or
- split the task into multiple files.
Stop conditions
If no compaction is needed under these rules, make no task changes and return control to the invoking workflow.
If compaction reveals a material unresolved question, stop and use spec-loop-clarify-task/SKILL.md.
When compaction is complete, return control to the workflow that invoked this skill.
Related skills
Lark MarkdownInstantly turn any markdown file into clean, formatted Lark/Figma-compatible documents without manual reformatting.488k
Lark DocCreate, read, update, summarize, rewrite and manage Feishu/Lark cloud documents directly from agent workflows.401k16.1kLark WikiCreate, organize, query, and manage documents, spaces, and members inside Lark (Feishu) knowledge bases directly from AI agent workflows.397k16.1k
Domain ModelingBuild and sharpen a project's domain model: pin down domain terminology in a glossary and record architectural decisions as ADRs.318k202k
Opensource Guide CoachGet expert, attribution-safe guidance on launching and sustaining an open-source project.270k71Readme I18nMaintain consistent, updatable language selector blocks across every README variant in a multilingual repository.270k71FAQ
What does it operate on?
A Spec Loop task file written in Markdown or AsciiDoc.
Why compact it?
To keep the spec small and local to the next step, per Spec Loop's design-first philosophy.