papperrollinggery/Paperrolling-DIRcreative-SKILL / skills/dircreative/checkpoint
dircreative-checkpoint
VerifiedSave and resume workflow state across phases, artifacts, and skill runs.
Checkpoint
Required Knowledge
Read only the reference needed for the active task, not this entire list. The root v2 route owns scope and authorization; legacy records do not add gates.
docs/film-preproduction/phase-contracts.yamldocs/film-preproduction/chat-inline-visualization-interface.mddocs/film-preproduction/schemas/skill-orchestration.yaml.dircreative/checkpoints/.dircreative/timeline.jsonl
Inputs
- current phase
- git status
- recent skill_run_receipt
- unresolved questions
Outputs
- checkpoint markdown
- timeline entry
- next exact action
Visual Decision Contract
When visualization adds clarity, use skills/dircreative/assets/visualizations/stage-surface-registry.json#checkpoint-current-state. Show current stage, locks, stale artifacts, unresolved decision, and next action from the audited current-state projection; resume intent must re-enter the active gate and preserve the Markdown fallback.
Rules
- Save current active phase, completed artifacts, verification status, blockers, and next command.
- Do not delete old checkpoints automatically.
- Keep checkpoint text actionable for another worker.
skill_run_receipt
Persist the following only for a requested formal handoff, pause/resume or actual execution record. Ordinary work returns its result without a separate receipt. The next skill is advisory; the controller continues only the requested scope.
Record checkpoint file path, active phase, unresolved questions, and next_recommended_skill.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |