Loading...
Loading...
Found 91 Skills
Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use for writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing backlog.
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.
Generate cinematic film-style video prompts for Seedance 2.0 (Higgsfield). Use this skill when users want AI videos with cinematic, film-like, movie-quality, Hollywood-style, dramatic, or professional film-quality. Trigger words: cinematic, film-like, movie scene, dramatic lighting, depth of field, lens flare, anamorphic, letterbox, film noir, epic, stabilized camera, dolly shot, crane shot, or any cinematic video generation request. Use this skill even if users don't explicitly say "cinematic" but describe film aesthetics.
This skill should be used when a developer wants to autonomously execute all tasks under a fully-specified Epic or Feature — for example "go", "start building", "implement everything", "run the loop", "execute the feature", "build it all", "kick it off". Requires that the Epic/Feature/Task tree is fully written before starting. Chains implement → verify → PR for every task in dependency order, with targeted human-in-the-loop gates for contradictions and ambiguities.
This skill should be used when a user wants to create a task, write a ticket, decompose a feature into implementable work, break down a story, define a vertical slice for development, or write Gherkin scenarios — for example "create a task", "write a task for this feature", "break this feature into tasks", "define implementation work", or "add a sub-issue to this feature". Guides creation of a GitHub Task issue linked to a parent Feature and Epic, derives Gherkin acceptance scenarios from the Feature's ACs, enforces DDD ubiquitous language in scenarios, and checks for vertical-slice integrity and task dependencies.
This skill should be used when a developer is ready to implement a GitHub Task issue and needs to read the full spec hierarchy (Task + Feature + Epic), explore the codebase, produce a concrete Technical Approach with real file paths, and drive TDD implementation against Gherkin scenarios. Triggers on phrases like "implement task
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).