frnkgns/Overgeared-Skills / skills/work-in-progress
work-in-progress
VerifiedWork in Progress
Create or Update WIP
Use work-in-progress/WIP-short-topic.md for meaningful unfinished work. Search for an existing related WIP first.
Include when applicable:
- Goal
- Current State
- Work Completed
- Remaining Work
- Current Approach
- Important Findings
- Discussion Context
- Decisions Made
- Rejected Approaches
- Files Being Worked On
- Problems / Blockers
- Testing / Verification
- Next Action
- Related Knowledge
- Change Audit (link to
changes/<note>.mdonce written) - Temporary Artifact Ledger (see below)
Preserve conclusions and reasoning, not chat transcripts. Update on meaningful progress, not every small edit.
Temporary Artifact Ledger
Track temporary development artifacts at the moment they are created, not by guessing at push time. Maintain this table in the active WIP note, and reflect it in the durable change audit.
## Temporary Artifact Ledger
| File | Type | Purpose | Remove Before Push | Cleanup Status |
|---|---|---|---|---|
| scripts/debug-api.ts | DEBUG | Inspect API response | Yes | Removed / Retained / Pending |
| db/seed-qa.ts | SEED | Create local QA records | Yes | Removed / Retained / Pending |
Types: TEST, QA, DEBUG, SEED, MOCK, FIXTURE, TEMP, LOCAL-ONLY.
This ledger follows the task until completion or push. When a temporary artifact is removed, update its Cleanup Status to Removed. When the change audit is written, mirror the Removal status into its Temporary Development Artifacts section.
Current Resume State
Maintain work-in-progress/current.md as the single canonical answer to "what were we doing, where did we stop, what is next?". Keep it small:
- Objective
- Current Status
- Completed
- In Progress
- Remaining
- Blockers
- Relevant Files
- Relevant Memory
- Next Recommended Step
Topic WIP notes may continue alongside it when several workstreams run in parallel; current.md links to them. When the work is finished, clear or archive the active state rather than leaving a misleading resume point.
current.md and the daily session note together must contain enough state to resume after an interruption or a compaction without the previous conversation.
Cooperation: WIP owns unfinished state and the next action. When context grows large, compaction condenses the thread and hands unfinished work here and durable findings to knowledge-vault; it never replaces this note. On resume, rebuild from this note plus relevant vault notes plus current source rather than trusting an old compacted summary.
Pause
When the user says pause, save where we are, continue later/tomorrow/next time, or equivalent:
- Find/create the relevant WIP.
- Record current state, completed and remaining work.
- Preserve meaningful decisions, rejected approaches, blockers, and actual verification status.
- Set one specific immediate
Next Action. - Refresh
work-in-progress/current.mdso the resume point is current. - Link relevant permanent knowledge.
- Save worthwhile unresolved investigations under
questions/. - Append the day's continuity entry to
sessions/YYYY-MM-DD.md.
Resume
When the user says continue, resume, revisit, or finish previous work:
- Find the matching WIP, and read
work-in-progress/current.mdwhen it exists. - Read Goal, Current State, Completed, Remaining, Discussion Context, Decisions, Rejected Approaches, Blockers, Testing, related questions/knowledge, and Next Action.
- Inspect current source code and verify the WIP still matches reality.
- Continue from the documented stopping point instead of restarting investigation.
- Update WIP as meaningful progress occurs.
Complete
When WIP is finished:
- Verify remaining work and testing.
- Promote reusable findings to permanent knowledge.
- Update architecture/ADRs/questions where needed.
- Move unresolved follow-up into another WIP.
- Clear or archive
work-in-progress/current.mdso no stale resume point remains. - Remove the WIP from active state; archive as
Status: Completedwith date/outcome if historically useful, otherwise delete after knowledge extraction. - Update the day's session note with the outcome.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |