papperrollinggery/Paperrolling-DIRcreative-SKILL / skills/dircreative
dircreative
VerifiedUse after explicit $dircreative for film concepts, stories, scripts, director or creative groups, shot/asset planning, reference-video analysis, and image/video prompts. Real media execution requires the corresponding authorization. Validated ADCO handoffs are supported. DIRcreative source maintenance is outside this Skill.
routes/fast-task.md
View on GitHub# Fast Task Route Card
Use for one bounded copy, shot, storyboard, prompt, or existing-artifact change.
## Budget
- One agent; zero Threads and zero Director Room.
- One task reference, zero full-project validation, zero specialized receipt.
- Zero routing or audit tool calls before an obvious standalone artifact.
- At least 75% of the answer should be the artifact or decision-useful craft.
## Execution
1. Preserve facts and decisions outside the requested edit.
2. Read only the selected task reference, if any.
3. Make the smallest complete professional change.
4. Return the revised result first. Add a short rationale only when it helps the
user judge the change.
5. Ask at most one question, only when the missing answer prevents a faithful
revision. Otherwise make a clearly labeled safe assumption.
Do not reopen intake, stage a confirmation sequence, persist state, or discuss
paths, Git, gates, receipts, hashes, validation, and internal roles unless the
user explicitly asks for that operational information.
Do not escalate a prompt-only or single-shot revision merely because it mentions
blocking, a reverse shot, or a camera. A request to compare or arrange a shared
scene’s people/camera relationship uses the root `spatial_discussion` layer.
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 |