Loading...
Loading...
Found 107 Skills
This skill should be used when the user asks to "create task", "add todo", "track action item", "create ticket", "new task", "remind me to", "need to do", "add to backlog", or mentions needing to track work items with priority and status in their secondbrain.
Creates a new numbered issue document in docs/issue/ following the project's standard issue format, and simultaneously creates the corresponding Korean translation in docs/dev/issue/. Use this whenever starting new work — features, bug fixes, tasks, or investigations. The user may say "create an issue", "new issue", "이슈 만들어줘", or simply describe work they want to start.
Manus-style file planning system for organizing and tracking progress of complex tasks. Creates three files: task_plan.md, findings.md, and progress.md. Use when users request planning, breaking down, or organizing multi-step projects, research tasks, or work requiring more than 5 tool calls. Supports automatic session recovery after /clear. Trigger phrases: task planning, project planning, create plan, break down task, multi-step planning, progress tracking, file planning, help me plan, break down project
Bootstrap lean multi-agent orchestration with beads task tracking. Use for projects needing agent delegation without heavy MCP overhead.
Create Linear issues. Use when creating bugs, tasks, or feature requests.
Decompose high-level objectives into atomic implementation tasks for Python/React projects. Use when breaking down large features, multi-file changes, or tasks requiring more than 3 steps. Produces independently-verifiable tasks with done-conditions, file paths, complexity estimates, and explicit ordering. Creates persistent task files (task_plan.md, progress.md) to track state across context windows. Does NOT cover high-level planning (use project-planner) or architecture decisions (use system-architecture).
AI-driven browser automation via Model Context Protocol
Use for planning work
Runs an autonomous development loop with research and implementation modes. Use when orchestrating iterative research and implementation cycles with dots-based task tracking and git workflow automation.
This skill should be used when the user asks to "track issues", "create beads issue", "show blockers", "what's ready to work on", "beads routing", "prefix routing", "cross-rig beads", "BEADS_DIR", "two-level beads", "town vs rig beads", "slingable beads", or needs guidance on git-based issue tracking with the bd CLI.
Audit tasks in docs/todo/done/ to verify claimed implementations actually exist in the codebase. Use when reviewing completed tasks, validating work before release, or periodically auditing task accuracy. Moves unverified tasks back to pending/.
Systematic framework for extracting actionable items from documents and organizing them into prioritized, trackable checklists. Use when converting reports, meeting notes, audits, or any document with embedded action items into structured TODO lists.