hefesto

Implement a story following its plan (future: bug, chore)

Create technical documentation for a story or feature

Create an implementation plan (auto-infers: feature, bug, chore)

Test a story or feature to verify the implementation works correctly

Create user-facing documentation for a story or feature

Manage features - create new ones, list existing, or accept completed features

Create a Product Requirements Document (PRD) for a feature

Generate user stories from a feature's PRD

Validate that a story or feature meets its requirements

Show dashboard with all features, stories, and development progress

Autonomous agent that validates code quality, test coverage, and documentation completeness for Hefesto-managed features and stories.

Provides guidance on writing effective technical documentation, including in-code docs (JSDoc, docstrings), API documentation, user guides, and READMEs. Activates when discussing documentation practices, writing docs, or improving documentation quality. Use for creating clear, maintainable documentation.

Planning strategy for bug fix stories. Activates when fixing defects, correcting unexpected behavior, or resolving errors. Use for root cause analysis with minimal surgical changes.

Planning strategy for maintenance and chore stories. Activates when refactoring code, updating dependencies, or performing technical maintenance. Use for behavioral-change-free improvements.

Planning strategy for feature stories. Activates when planning new functionality, capabilities, or user-facing features. Use for multi-phase implementation planning with user value focus.

Provides testing best practices, strategies, and patterns for unit, integration, and end-to-end testing. Activates when discussing test approaches, test coverage, testing frameworks, mocking strategies, or test-driven development. Use for guidance on writing effective tests and achieving quality coverage.

Provides guidance on defining acceptance criteria, quality gates, and validation requirements for software features. Activates when discussing acceptance criteria, definition of done, quality requirements, or validation strategies. Use for creating clear, testable requirements and quality standards.