Loading...
Loading...
Found 81 Skills
Phase-level planning workflow for planner agents. Handles reading templates, exploring codebase references, creating plan.md and phase files, self-validation, and checkpoint reporting to the orchestrator. Invoke this skill as your first action — not user-invocable.
Implement tasks from the change, writing actual code following the specs and design. Trigger: When the orchestrator launches you to implement one or more tasks from a change.
Clickup integration. Manage project management and ticketing data, records, and workflows. Use when the user wants to interact with Clickup data.
Automatically updates terminal window title to reflect the current high-level task. Use at the start of every Claude Code session when the user provides their first prompt, and whenever the user switches to a distinctly new high-level task. Helps developers manage multiple Claude Code terminals by providing clear, at-a-glance identification of what each terminal is working on.
This skill applies when the user wants to resume previous work, enters the command "/vibe-continue", or starts a new session and needs to load saved context. Restore from shared task facts first, then use task.md as the local handoff.
One-time project onboarding for swain. Migrates existing CLAUDE.md content to AGENTS.md (with the @AGENTS.md include pattern), verifies vendored tk (ticket) for task tracking, configures pre-commit security hooks (gitleaks default), and offers to add swain governance rules. Run once when adopting swain in a new project — use swain-doctor for ongoing per-session health checks.
Cross-cutting project status dashboard. Shows active epics with progress ratios, actionable next steps, blocked items, in-progress tasks, GitHub issues, and session context. Produces rich terminal output with clickable links. Triggers on: 'project status', 'swain status', 'what's next', 'dashboard', 'overview', 'where are we', 'what should I work on', 'am I blocked', 'what needs review', 'show me priorities'.
Tracked lightweight execution with composable rigor flags for tasks between a typo fix and a full feature. Plan + execute with optional --discuss, --research, and --full flags to add rigor incrementally. Use for "quick task", "small change", "ad hoc task", "add a flag", "extract function", "small refactor", "fix bug in X". Do NOT use for multi-component features, architectural changes, or anything needing wave-based parallel execution — those are Simple+ tier.
Deterministic plan lifecycle management via scripts/plan-manager.py: create, track, check, complete, and abandon task plans. Use when user says "/plans", needs to create a multi-phase plan, track progress on active plans, or manage plan lifecycle (complete, abandon, audit). Do NOT use for one-off tasks that need no tracking, feature implementation, or debugging workflows.
Execute and implement approved specification proposals in sequence with testing and verification as the priority. It is used for implementing changes, applying proposals, executing specification tasks, or building according to approved plans. Trigger words include "openspec development", "development", "implementation", "implement proposal", "apply change", "execute specification", "complete tasks in order", "build feature", "start implementation"
Implement the tasks in a spec-driven change. Works through incomplete tasks one by one, marking each complete as it goes.
Use when you need to execute I1 (Implementation Plan) in the Spec Pack of sdlc-dev, convert requirements/design into `{FEATURE_DIR}/implementation/plan.md` (the single source of truth for execution checklist and status, SSOT), and provide an unambiguous task list for subsequent I2 execution.