Loading...
Loading...
Found 100 Skills
Set up a Markdown-based local ticket management system for your project. Create task, bug, and chapter tickets in the .local/ticket/ directory, and track progress using checklists. It can be used casually since it is not managed by Git. Language and framework agnostic. Use when requested: "introduce ticket system", "task management with Markdown", "set up local ticket management", "create ticket", "create bug ticket", "create chapter", "create epic", "local ticket system", "setup ticket management".
GainForest beads (`bd`) planning workflow. Activates on ALL user work requests — task planning, epic management, claiming work, closing tasks with commit links, handling blockers. Use before writing any code.
This skill should be used when the user asks to "use delphi", "ask delphi", or wants multiple parallel oracle investigations of the same question to discover divergent insights. Delphi delegates to multiple oracle workers simultaneously with identical prompts, allowing them to independently explore and potentially discover different paths, clues, and solutions. Results are saved as tickets tagged research,delphi and synthesized into an epic ticket.
Issue linking, blockers, and dependency analysis. TRIGGERS: 'what's blocking', 'what is blocking', 'is blocked by', 'link issues', 'link to', 'blockers for', 'depends on', 'clone issue', 'clone with', 'blocking chain', 'dependency graph', 'show dependencies', 'get blockers', 'relates to', 'duplicates'. Use for issue dependencies, relationships, and cloning. NOT FOR: epic linking (use jira-agile), field updates (use jira-issue), bulk cloning (use jira-bulk).
Work decomposition, dependency ordering, and status tracking for software tasks. Activate when breaking down features into tasks, managing work items, tracking dependencies, creating stories or epics, or asking what to work on next. Works with any task tool: harness-native todos, dot CLI, GitHub Issues, or file-based tracking.
Use when modifying an existing em plan or task files. Triggers on: "update em", "change plan", "modify epic", "add task", "remove task", "rename phase", "apply annotations", "edit plan". Applies inline > and >> annotations or accepts conversational changes to plan.md or task milestone files.
Generates the Data Engineering team weekly/sprint status report from Azure DevOps. Organized by Epic, with objectives, on/off track status, risks, completed and planned items per area, clickable ADO links, and unplanned items flagged. Use when the user asks for a Data Engineering sprint report, weekly report, current sprint status, activities report, or sprint summary.
Use when working with the beads (bd) CLI for issue tracking, managing epics and tasks, handling dependencies, or starting/ending coding sessions with persistent work tracking
Execute a plan file or Beads epic systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan, working through a spec, following documented steps, or executing a Beads issue ID (e.g., bd-123, gno-45, app-12).
Autonomous SDLC router. Takes a job, classifies complexity, executes the appropriate lev-* workflow (from trivial fix to full epic), and returns "done" with runnable instructions. One shot to full auto: spec/bd/poc/impl. Subagent returns completion artifact. Triggers: "sidequest", "side quest", "just do it", "autonomous", "one shot"
Access health records with MyChart - view medical records, messages, and appointment information
BF 워크플로우의 사람-시스템 경계 허브. orchestrate를 모드별로 스폰하고, 에픽 단위 루프를 돌며 사람과 소통하는 유일한 경계이다.