Loading...
Loading...
Found 14 Skills
No Polling for Background Agents
Harness Engineering Phase 3: Establish cross-session state management to solve the problem of agents forgetting previous conversations. Create three files: tasks.json (task list), progress.md (progress record), and init.sh (environment initialization script). Use this skill immediately when the user says phrases like "establish task management", "make agent remember progress", "create tasks.json", "maintain state across sessions", "agent doesn't remember what was done last time", "create progress file", or "initialize state management". Prerequisites: harness-step1 and harness-step2 have been completed (the project has AGENTS.md and docs/ knowledge base).
Comprehensive codebase research skill. Documents codebase as-is by spawning parallel sub-agents and synthesizing findings into research documents.
Manage work in Vibe Kanban (VK), the shared source of truth for agent tasks. Use when checking assigned work, creating/updating tasks, running heartbeat checks, scanning @mentions, or producing daily standup summaries. Triggers: "check the board", "what's on my plate", "create/update task", "heartbeat", "standup summary".
Create implementation plans with tasks grouped by subsystem. Related tasks share agent context; groups parallelize across subsystems.
Parallel Agent Orchestration
Refines a v1 project plan into agent-ready tasks with clear context, implementation steps, and validation criteria. Use after /plan-project has produced a v1 plan.
Maintain a structured ledger of decisions, discovered bugs and fixes, user preferences, constraints, current status, and failed approaches throughout multi-step agentic tasks. Auto-update after every significant step. Triggers on "where were we", "continue", "summarize status", "remember", or when a new agent instance takes over a task.
Use when finding and claiming tasks. Matches tasks to your declared capabilities for optimal assignment.
Create, query, update, assign, and discuss Multica issues. Also covers comments, subscribers, and viewing execution runs for an issue. Use when the user wants to file a task for an agent, triage the board, comment on an issue, or inspect what an agent actually did.
Capture the current task into a structured temporary session bundle under `.agents/sessions/` so a learning agent can later distill durable repo knowledge. Use for completed, blocked, or abandoned tasks with meaningful changes, debugging, validation, or reusable lessons.
Beads (bd) distributed git-backed issue tracker for AI agents: hash-based IDs, dependency graphs, worktrees, molecules, sync, GitLab/Linear/Jira. Keywords: bd, beads, issue tracker, git-backed, dependencies, molecules, worktree, sync, AI agents.