Loading...
Loading...
Found 38 Skills
[Utilities] ⚡⚡⚡⚡⚡ Bootstrap a new project step by step
Capture explored work as a backlog item for future implementation. Use when you've explored an enhancement, alternative approach, or feature but decided to defer it. Creates comprehensive plan files in backlog/ directory with enough context for a future session to execute efficiently.
TODO.md file output template examples for todo-task-planning command. Provides structured checklist format with task classification, status indicators, and research rationale.
Before executing a task, analyze the available tool set (web search, code execution, file read/write, API calls, database queries, memory tools), select the optimal tools, plan execution order, and prevent unnecessary tool calls. Triggers on multi-step tasks, "which tool should I use", "plan the tools", or whenever multiple tools could apply.
Plan mode: write markdown plan to .hermes/plans/, no exec.
Interactive planning and execution for complex tasks. Use when user asks to use or invoke planner skill.
Internal conversation-entry router for Claude Code. Performs a lightweight intake pass at the start of substantive work: decide whether a more specific skill should be invoked first, whether specialized agent delegation is warranted, how much context is actually needed, and whether the task needs planning or can proceed directly. Not a user-facing slash command.
Use when goals, capabilities, and epics are defined and you need to decompose them into features, user stories, acceptance summaries, and cross-functional delivery tasks. Supports `--quick-flow` for fast assumption-driven execution and `--full-flow` for question-driven verified execution. Explicit full or end-to-end spec refinement requests continue through the existing 18-stage refinement cascade.
Load this skill when the user mentions `ulw` or `ultrawork`.
[Dev] Extracts and organizes best practices for a given topic into a minimal tree structure (max depth 3, max 5 children per node). Use during task planning when writing subtasks in Docs/{name}_Task.md - output is added under each subtask as a concise reference guide. Pure reasoning task with strict formatting rules: keywords/noun phrases only, no prose. (project)
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the codebase or domain is unfamiliar, the user will "know it when they see it", a reference implementation must be understood before porting, mid-build deviations from the plan need capturing, or a finished change needs buy-in or verified understanding before merge. Pairs with [write-spec](../write-spec/SKILL.md) — walk the quadrants to burn off fog before slicing, and feed the finished map into the spec.
This skill should be used when a user wants to plan and create the complete set of Tasks for a Feature all at once, systematically walk through every implementable slice of work for a Feature, or create tasks in batch with step-by-step confirmation. Triggers on phrases like "plan all tasks for this feature", "create all tasks for feature