From prism-devtools
Use when creating new Epic documents. Groups related user stories, includes risk analysis, integration points, and story breakdown with PROBE estimation.
npx claudepluginhub resolve-io/.prismThis skill uses the workspace's default tool permissions.
- When starting a new major feature or initiative
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Provides patterns for autonomous Claude Code loops: sequential pipelines, agentic REPLs, PR cycles, de-sloppify cleanups, and RFC-driven multi-agent DAGs. For continuous dev workflows without intervention.
Applies NestJS patterns for modules, controllers, providers, DTO validation, guards, interceptors, config, and production TypeScript backends with project structure and bootstrap examples.
core-config.yamlTo create a new Epic document that groups related user stories into a cohesive unit of work. Epics represent large features or initiatives that deliver significant business value and typically span multiple sprints. This task ensures epics are properly structured with clear goals, risk analysis, integration points, and a well-defined story breakdown.
../core-config.yaml (relative to tasks folder) if it existsepicLocation, devStoryLocation, prd.*, architecture.*docs/epics/ for epics, docs/stories/ for storiesdocs/prd.md or sharded PRD location)If creating a new epic (not from PRD), gather:
If the epic involves migration or upgrade work:
Assess and document risks:
Document how this epic integrates with:
Break the epic into user stories following these principles:
| Size | Points | Typical Duration | Description |
|---|---|---|---|
| XS | 1 | 1-2 hours | Trivial change, single file |
| S | 2 | 2-4 hours | Small change, few files |
| M | 3 | 4-8 hours | Moderate complexity |
| L | 5 | 1-2 days | Significant work |
| XL | 8 | 2-3 days | Complex, consider splitting |
Create the epic document using epic-tmpl.yaml:
If requested, create individual story files:
story-tmpl.yaml as the template{devStoryLocation}/{epic-id}/ subdirectory{epicLocation}/{epic-id}.md