hero-engine
Official@hero-engine
hero-engine provides 152 agent skills spanning product management frameworks, QA test design, multi-language engineering guidance, and sales qualification for software delivery teams.
Agent Skills by hero-engine
Showing 127 vetted skills indexed across 1 GitHub repositories.
hero-engineexec-narrative
Writes Amazon-style six-page narrative memos with paragraph-level argument pressure-testing.
hero-engineassumption-testing
Designs pre-registered assumption tests for desirability, viability, feasibility, and usability risks.
hero-enginecontinuous-discovery-cadence
Establishes a weekly continuous discovery rhythm of customer touchpoints, opportunity revisits, and assumption tests.
hero-enginestory-mapping
Builds Jeff Patton user story maps with backbones, walking skeletons, and release slices.
hero-enginepm-preset-detection
Reads hero.json pm.presets config and applies preset-specific authoring rules per artifact type.
hero-engineprioritization-frameworks
Applies RICE, ICE, WSJF, and value-vs-effort frameworks to rank product backlogs with auditable scoring.
hero-enginerelease-notes-writing
Writes customer-facing and internal release notes from shipped spec records.
hero-enginestory-writing-invest
Validates user stories against the INVEST quality framework before engineering handoff.
hero-enginepitch-writing-shape-up
Guides authoring of Shape Up pitches with appetite budgets, fat-marker sketches, rabbit holes, and no-gos.
hero-enginepositioning-canvas
Derives product market positioning through April Dunford's five-component ordered canvas.
hero-enginehandoff-protocol
Executes PM-to-engineering spec handoffs via owner flips with pre-flight gates and bitemporal history.
hero-enginelaunch-gtm-tiering
Sizes product launches into impact tiers and scopes the go-to-market checklist accordingly.
hero-engineevidence-synthesis
Synthesize customer signals into attributed evidence sections for product initiatives and PRDs.
hero-enginecapacity-planning
Calculates team capacity and draws Story Queue cut-lines across sprint, cycle, kanban, and phased delivery presets.
hero-enginemetrics-design
Define measurable product success metrics with baselines, targets, and engineering-verified observability.
hero-engineepic-framing
Frames epics as coherent bets with shared outcomes, rollup acceptance criteria, and sequenced child features.
hero-enginemetric-rca
Localize metric changes through decomposition, drift classification, and causality checks.
hero-enginedomain-glossary-maintenance
Maintains a shared PM and engineering domain glossary as a versioned knowledge entry in .hero/knowledge.
hero-enginerisk-surfacing
Write actionable product risks as scenario, indicator, and response for PRDs and roadmaps.
hero-engineacceptance-criteria-ears
Writes testable acceptance criteria using the five EARS requirement patterns.
hero-enginesprint-planning
Guides sprint commit sizing, velocity distribution analysis, and cut-line decisions for story queues.
hero-engineopportunity-assessment
Evaluates product opportunities using Cagan's 10-question assessment with single-challengeable-assumption discipline.
hero-enginestakeholder-communication
Adapt PM artifacts into audience-specific cuts for executives, customers, engineering, and sales.
hero-enginepm-agent-doctrine
Enforces corpus-grounding, human decision gates, and compare-don't-replace synthesis across PM agent outputs.
Frequently Asked Questions About hero-engine
FAQPage SchemaWhat tasks can I automate using hero-engine's skills?▼
You can automate product discovery (Torres-style opportunity solution trees, assumption tests), spec authoring (PRDs, EARS/Gherkin acceptance criteria, story mapping), QA design (boundary-value analysis, regression scoring, flake triage), engineering delivery (stack detection, migration safety, PR review), and sales qualification (MEDDPICC, SPIN discovery, forecast methodology).
Who are hero-engine's skills designed for?▼
The skills target specialized agent personas: product strategists, PRD authors, story writers, discovery researchers, QA test architects, delivery leads, debug investigators, migration engineers, forecast analysts, deal strategists, and buyer researchers — each loading role-specific framework guidance.
How do hero-engine skills operate at runtime?▼
Skills are loaded on demand by agents and commands — stack-detection routes engineering work to language-specific guidance, pm-preset-detection reads hero.json config to apply sprint, cycle, kanban, or phased rules, and handoff protocols flip artifact ownership from PM to engineering with bitemporal history.
What prerequisites do hero-engine skills require?▼
Skills assume a Hero workspace with hero.json configuration for PM presets, a .hero/knowledge directory for domain glossaries and explainers, and a knowledge graph for cross-domain queries between PM artifacts and engineering reality. Some skills depend on deferred Wave-2/Wave-3 agents.
Do hero-engine skills make autonomous decisions?▼
No. The pm-agent-doctrine mandates that all suggestions are reversible, human-gated proposals grounded in the team's own corpus — never auto-decisions. Duplicate detection never auto-merges, test triage requires human confirmation, and the /drive autonomy boundary stays deterministic via needs_me pauses.