Loading...
Loading...
Found 39 Skills
Used when executing implementation plans containing independent tasks in the current session
Run /develop to build a feature, UI or backend, from an approved design, a page, component, API, service, or data slice. If something load bearing is undecided and no spec records it, it stops and routes you to /architect; otherwise it reads the spec plus AGENTS.md, builds, and advances the scope.
Apply SPARC methodology (Specification, Pseudocode, Architecture, Refinement, Completion) for systematic development. Use for feature development, TDD workflows, and structured problem-solving.
Use after exploring completes or whenever a feature already has locked requirements and now needs research, synthesis, phase definition, story mapping, and executable task beads. Use for prompts like "plan this", "break this into tasks", "decompose this work", "map the stories", "research and plan", or "turn this into beads" before implementation begins.
Comet Preset Path: Bug fix / Hotfix. Skip brainstorming, go directly through open → build → verify → archive. Applicable for behavior fixes and scenarios that do not involve new capability design.
Complete workflow for developing new features from design to deployment. Use when starting a new feature, adding functionality, or building something new.
Install and configure Oh My Hermes workflow layer for building, shipping, and operating apps with Hermes Agent
Software development based on Extreme Programming (XP). Use it when implementing software features of any kind. Coordinates planning, TDD, refactoring, and commits.
Use when starting any implementation task, feature request, bug fix, or refactoring work. Triggers on /plan command, before any code is written, when requirements need structured analysis, or when transitioning from brainstorming to implementation. Forces question-asking, approach comparison, and explicit approval before any code.
Execute one scoped change: understand the task, make the smallest complete implementation, test it, verify it, and report.
End-to-end orchestration for non-trivial software feature development. Use this skill whenever the user asks to implement a PR-sized feature, break down a plan, have subagents review a plan, run a plan-review-development-acceptance loop, coordinate multiple review perspectives, produce an acceptance report, or generate an HTML PR summary. Prefer this skill for multi-step code changes even if the user only says "build this feature" and the task is not a tiny one-file edit.
Use when stories and clarified delivery context are ready and you need to produce a structured delivery specification that engineering and cross-functional teams can use for implementation planning and handoff. 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.