From nanoclip
Core NanoClip work cycle protocol and task management. Use when you need to check assignments, update task status, create subtasks, post comments, or coordinate with other agents. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for NanoClip coordination.
How this skill is triggered — by the user, by Claude, or both
Slash command
/nanoclip:nanoclipThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You run in **work cycles** — execution windows triggered by the NanoClip orchestrator. Each cycle, you wake up, check your assigned tasks, do useful work, and exit. You do not run continuously.
You run in work cycles — execution windows triggered by the NanoClip orchestrator. Each cycle, you wake up, check your assigned tasks, do useful work, and exit. You do not run continuously.
Your agent ID is in the NANOCLIP_AGENT environment variable. The organization directory is in NANOCLIP_COMPANY_DIR. Your full agent config is at $NANOCLIP_COMPANY_DIR/.nanoclip/agents/$NANOCLIP_AGENT.json.
Follow these steps every time you wake up:
Step 1 — Identity. Read your agent config to understand your title, capabilities, expertise, and reporting chain.
Step 2 — Get assignments. Check your assigned tasks by reading .nanoclip/tasks/*.json files where assignee matches your agent ID and status is todo, in_progress, or blocked.
Step 3 — Pick work. Prioritize:
in_progress tasks first (continue where you left off)todo tasks second (start new work)blocked tasks only if you can unblock themStep 4 — Do the work. Update the task status to in_progress, then do the actual work in the workspace/ directory — write real code, create real files, run tests.
Step 5 — Update status. When done, update the task to done with a comment describing what you did. If blocked, set to blocked with a clear explanation.
Step 6 — Delegate if needed. If you're a manager, create subtasks and assign them to your reports.
backlog — Not yet ready for worktodo — Ready to be picked upin_progress — Currently being worked ondone — Completedblocked — Can't proceed; needs external actioncancelled — Abandonedcritical > high > medium > low
--parent when creating subtasks.workspace/. Don't just plan.blocked with a clear comment.in_progress and unfinished, leave a comment explaining status and next steps.npx claudepluginhub bryonjacob/nanoclip --plugin nanoclipManages Chorus dev workflow: claim tasks, report progress, self-check criteria, submit for review, and handle sub-agent sessions with Claude Code Agent Teams.
Orchestrates multi-agent parallel execution for complex tasks like features, refactoring, testing, reviews, and documentation using cc-mirror tracking and TodoWrite visibility.
Manages tasks via the taskwarrior CLI with annotations that reference markdown files, inline notes, and a Python script for opening task-related documents.