From prism-devtools
Use when Dev agent needs to implement fixes based on QA gate results. Reads QA outputs, creates prioritized fix plans, and applies code/test changes to address identified issues.
npx claudepluginhub resolve-io/.prismThis skill uses the workspace's default tool permissions.
<!-- Powered by PRISMâ„¢ System -->
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.
Implement fixes based on QA results (gate and assessments) for a specific story. This task is for the Dev agent to systematically consume QA outputs and apply code/test changes while only updating allowed sections in the story file.
deno lint and deno test -A until cleanrequired:
- story_id: '{epic}.{story}' # e.g., "2.2"
- qa_root: from `../core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`)
- story_root: from `../core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`)
optional:
- story_title: '{title}' # derive from story H1 if missing
- story_slug: '{slug}' # derive from title (lowercase, hyphenated) if missing
{qa_root}/gates/{epic}.{story}-*.yml
{qa_root}/assessments/{epic}.{story}-test-design-*.md{qa_root}/assessments/{epic}.{story}-trace-*.md{qa_root}/assessments/{epic}.{story}-risk-*.md{qa_root}/assessments/{epic}.{story}-nfr-*.mddeno lintdeno test -A../core-config.yaml and resolve qa_root and story_root{story_root}/{epic}.{story}.*.md
gate (PASS|CONCERNS|FAIL|WAIVED)top_issues[] with id, severity, finding, suggested_actionnfr_validation.*.status and notestrace coverage summary/gapstest_design.coverage_gaps[]risk_summary.recommendations.must_fix[] (if present)Apply in order, highest priority first:
top_issues (security/perf/reliability/maintainability)coverage_gaps (prioritize P0 scenarios if specified)must_fix recommendationsGuidance:
deps.ts (see docs/project/typescript-rules.md)src/core/di.ts and existing patternsdeno lint and fix issuesdeno test -A until all tests passCRITICAL: Dev agent is ONLY authorized to update these sections of the story file. Do not modify any other sections (e.g., QA Results, Story, Acceptance Criteria, Dev Notes, Testing):
Status Rule:
Status: Ready for DoneStatus: Ready for Review and notify QA to re-run the reviewreview-story to update the gate../core-config.yamlstory_idtop_issues addressedGiven gate docs/project/qa/gates/2.2-*.yml shows
coverage_gaps: Back action behavior untested (AC2)coverage_gaps: Centralized dependencies enforcement untested (AC4)Fix plan:
deps.ts