By elafo
Complete software development lifecycle management: features, PRDs, user stories, planning, coding, testing, validation, and documentation
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
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.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Complete software development lifecycle management plugin for Claude Code. Named after Hephaestus (Hefesto in Spanish), the Greek god of craftsmanship and forge.
Hefesto provides a structured workflow for managing software features from conception to completion. It uses a two-namespace architecture separating Product Owner (PO) and Developer (DEV) responsibilities, with router commands that apply strategies based on the target entity type.
| Namespace | Responsibility | Semantic |
|---|---|---|
po: | Product Owner | The "what" - requirements, validation, acceptance |
dev: | Developer | The "how" - planning, coding, testing |
Commands like dev:test, po:validate, and dev:document are routers that detect the target type and apply the appropriate strategy:
dev:test .hefesto/features/.../stories/001-login
↳ Detected: story → Story Testing Strategy
dev:test feature 2025-01-15-user-auth
↳ Explicit: feature → Feature Testing Strategy
# Use as plugin directory
claude --plugin-dir /path/to/hefesto
# Or add to project
cp -r hefesto /your/project/.claude-plugin/
| Command | Description | Type |
|---|---|---|
po:feature | List features | Router |
po:feature create <desc> | Create new feature | Subcommand |
po:feature accept <id> | Accept completed feature | Subcommand |
po:prd <feature_id> | Create PRD | Simple |
po:stories <feature_id> | Generate user stories | Simple |
po:validate <path> | Validate requirements met | Router (story/feature) |
po:document <path> | User-facing documentation | Router (story/feature) |
| Command | Description | Type |
|---|---|---|
dev:plan <path> | Implementation planning | Router (story) |
dev:code <path> | Code implementation | Router (story) |
dev:test <path> | Testing | Router (story/feature) |
dev:document <path> | Technical documentation | Router (story/feature) |
| Command | Description |
|---|---|
status | Dashboard with all features and progress |
┌─────────────────────────────────────────────────────────────┐
│ PRODUCT OWNER │
├─────────────────────────────────────────────────────────────┤
│ po:feature create → po:prd → po:stories │
│ ↓ │
├─────────────────────────────────────────────────────────────┤
│ DEVELOPER │
├─────────────────────────────────────────────────────────────┤
│ dev:plan → dev:code → dev:test → dev:document │
│ (story) (story) │
│ ↓ │
├─────────────────────────────────────────────────────────────┤
│ PRODUCT OWNER │
├─────────────────────────────────────────────────────────────┤
│ po:validate story → po:document story │
│ ↓ │
│ [after all stories complete] │
│ ↓ │
├─────────────────────────────────────────────────────────────┤
│ DEVELOPER │
├─────────────────────────────────────────────────────────────┤
│ dev:test feature → dev:document feature │
│ ↓ │
├─────────────────────────────────────────────────────────────┤
│ PRODUCT OWNER │
├─────────────────────────────────────────────────────────────┤
│ po:validate feature → po:document feature → po:feature accept │
└─────────────────────────────────────────────────────────────┘
npx claudepluginhub eLafo/hermes --plugin hefestoContext Engineering framework for Claude Code. Provides comprehensive context management capabilities based on C = A(c₁, c₂, c₃, c₄, c₅, c₆) framework including context creation, analysis, validation, and lifecycle management.
eLafoGestión unificada de múltiples fuentes de contexto
AI Coding Agent - PRD to tasks to implementation loop
oskarhaneSpec-driven development for big features. When features get too big, plan mode gets too vague—leading to hallucinations during implementation. ShipSpec replaces vague plans with structured PRDs, technical designs, and ordered tasks that keep Claude grounded.
jsegovProduct management: ticket-info, user-stories-create, prd, spec
ai-driven-devSpecification-driven development workflow: specify → plan → tasks → implement
deepeshBodhAI-powered cascading development framework with design document system and multi-agent collaboration. Breaks down projects into Features (Mega Plan), Features into Stories (Hybrid Ralph), with auto-generated technical design docs, dependency-driven batch execution, Git Worktree isolation, and support for multiple AI agents (Codex, Amp, Aider, etc.).
Taoidle'MUST BE USED PROACTIVELY when user mentions: planning, PRD, product requirements document, project plan, roadmap, specification, requirements analysis, feature breakdown, technical spec, project estimation, milestone planning, or task decomposition. Use IMMEDIATELY when user says "create a PRD", "plan this feature", "document requirements", "break down this project", "estimate this work", "create a roadmap", "write specifications", or references planning/documentation needs. Expert Technical Project Manager that creates comprehensive PRDs with user stories, acceptance criteria, technical architecture, task breakdowns, and separate task assignment files for sub-agent delegation.'
ccplugins