Loading...
Loading...
Found 12 Skills
AIWorkflowOrchestratorの正本仕様を `references/` から検索・参照・更新するスキル。 resource-map / quick-reference / topic-map / keywords を起点に、必要最小限の文書だけを段階的に読む。 用途: 要件確認、設計/API/IPC契約確認、UI/状態管理/セキュリティ判断、task-workflow・lessons-learned・未タスク同期。 特に safeInvoke timeout、settings bypass、skill lifecycle、global nav、Skill Center / Workspace / Agent / Skill Creator の導線再編を扱う。 Anchors: • Specification-Driven Development / 適用: 正本仕様同期 / 目的: 実装-仕様整合の維持 • Progressive Disclosure / 適用: resource-map起点読込 / 目的: 必要最小限参照で漏れ防止 Trigger: 仕様確認, 仕様更新, task-workflow同期, lessons-learned同期, UI仕様反映, API/IPC契約確認, セキュリティ要件確認, safeInvoke, timeout, settings bypass, skill lifecycle, Skill Center, Workspace, Agent, Skill Creator, navContract, GlobalNavStrip, MobileNavBar, SkillManagementPanel, line budget reform, spec splitting, family split, generated index sharding
Task management skill for the Agent Kanban CLI — claim, log, complete tasks
Apply OpenSpec OPSX in a strict one-task-at-a-time loop. Use when the user asks to execute work as single-task changes, wants spec-first implementation per task, or says to use OpenSpec method for each task from a task list. Supports both native /opsx command environments and manual fallback by creating OpenSpec artifact files directly.
Manage tasks via Overseer codemode MCP. Use when tracking multi-session work, breaking down implementation, or persisting context for handoffs.
CRITICAL skill for executing multiple runSubagent calls in a SINGLE function_calls block for true parallelism. Essential for efficient multi-task workflows, subagent coordination, and maximizing throughput.
Manage tickets with tk CLI. Triggers on "create ticket", "list tickets", "what's next", "blocked", "close ticket", "ticket status", "work on next ticket/issue".
Mandatory only on the task-file path of `spec-loop-plan-task`. Use when an active task file already exists and the next user-facing action would otherwise present that task for evaluation, feedback, review, or implementation approval.
Implement work on issues. Use when user asks to "start working on issue", "what should I work on", "pick up task", "continue work", or "find next task".
Use Probe to interact with Nexus via CLI commands. Agents use probe for Zenon Network wallet creation, auth, ideas, projects, tasks, claims, PR/issue linking, messaging, daemon liveness, and SQL inspection. Use when you need to (1) create or manage project artifacts (ideas, projects, tasks), (2) claim and execute tasks with PR delivery, (3) maintain online presence and heartbeats, or (4) inspect Nexus state via SQL.
Work a task end-to-end with lean context gathering, implementation, and verification
Standard implementation workflow for all coding tasks. Executes a systematic 5-phase cycle: Investigate → Plan → Implement → Verify → Complete. Integrates Serena think checkpoints, introspection markers, and quality gates. Supports --frontend-verify flag for browser/app/CLI visual verification. Use when: - User asks to implement a feature, fix a bug, or refactor code - User provides a task that requires code changes - User says "do this", "build this", "fix this", "add this" - Any implementation work involving code editing Keywords: task, implement, build, fix, add, create, refactor, update, change
Wrap up current task — commit, update Linear, optionally create PR, route to next