dfrysinger
38 verified skills716 total stars
test
Use when implementation is complete (after Integrate in full pipeline, after Implement in quick fix) — runs acceptance testing against goals, routes failures through fix pipeline, handles phase completion and PR creation
development19
plan
Use when prior artifacts are approved and the QRSPI pipeline needs detailed task specs — breaks structure into ordered tasks with test expectations, dependencies, and LOC estimates (full pipeline requires design+structure; quick fix requires only goals+research)
development19
build/skills/prompt-prose-writer
Apply prompt-design rules when authoring or planning prompt-prose deliverables. Detects whether a deliverable IS prompt prose, and only then Reads the rules and applies R1-R7 before drafting. Preloaded by agent files that may author prompt prose.
development19
skills/prompt-prose-reviewer
Apply prompt-design rules when reviewing prompt-prose subjects in a diff. Detects which files (or sub-blocks) are prompt prose, applies R1-R7 + cross-cutting principles + finding-type gate, and emits findings with proper change_type tagging. Preloaded by reviewer agents that may encounter prompt prose in their review subject.
testing19
research
Use when questions.md is approved and the QRSPI pipeline needs objective codebase and web research — dispatches parallel specialist subagents per question, collates per-question findings into research/summary.md
development19
goals
Use when starting a new QRSPI pipeline run — captures user intent and constraints through interactive dialogue, then synthesizes a problem-framed goals.md
development19
structure
Use when design.md is approved and the QRSPI pipeline needs file/component mapping — maps vertical slices to specific files, interfaces, and component boundaries
testing19
build/skills/prompt-prose-reviewer
Apply prompt-design rules when reviewing prompt-prose subjects in a diff. Detects which files (or sub-blocks) are prompt prose, applies R1-R7 + cross-cutting principles + finding-type gate, and emits findings with proper change_type tagging. Preloaded by reviewer agents that may encounter prompt prose in their review subject.
development19
questions
Use when goals.md is approved and the QRSPI pipeline needs research questions generated — produces tagged questions that guide the Research step without leaking goals
development19
design
Use when research/summary.md is approved and the QRSPI pipeline needs an architecture — proposes approaches, surfaces key architectural decisions with rationale, and defines a design-level test strategy through interactive design discussion
testing19
reviewer-protocol
Cross-cutting QRSPI reviewer protocol — finding schema, change-type classifier, untrusted-data handling, and dispatch contract. Per-channel emission contracts live in sibling files first-party-emission.md and third-party-emission.md.
development19
design
Use when research/summary.md is approved and the QRSPI pipeline needs an architecture — proposes approaches, surfaces key architectural decisions with rationale, and defines a design-level test strategy through interactive design discussion
testing19
replan
Use between phases when Test signals more phases remain — analyzes completed phase, proposes task updates with severity classification, handles minor updates or major backward loops
testing19
research
Use when questions.md is approved and the QRSPI pipeline needs objective codebase and web research — dispatches parallel specialist subagents per question, collates per-question findings into research/summary.md
development19
test
Use when implementation is complete (after Integrate in full pipeline, after Implement in quick fix) — runs acceptance testing against goals, routes failures through fix pipeline, handles phase completion and PR creation
development19
replan
Use between phases when Test signals more phases remain — analyzes completed phase, proposes task updates with severity classification, handles minor updates or major backward loops
testing19
reviewer-protocol
Cross-cutting QRSPI reviewer protocol — finding schema, change-type classifier, untrusted-data handling, and dispatch contract. Per-channel emission contracts live in sibling files first-party-emission.md and third-party-emission.md.
development19
using-qrspi
Use when starting any conversation — establishes the QRSPI pipeline for agentic software development, requiring structured progression through Goals, Questions, Research, Design, Phasing, Structure, Plan, Parallelize, Implement, Integrate, Test, with Replan firing between phases
development19
parallelize
Use when plan.md is approved and the QRSPI pipeline needs a parallelization plan — analyzes task dependencies and file overlap, decides execution mode, produces parallelization.md with a symbolic branch map; hands off to Implement
testing19
integrate
Use when all current-phase tasks are implemented — merges task branches, runs cross-task integration review, security review, and CI gate
testing19
implementer-protocol
Cross-cutting QRSPI implementer protocol — dispatch shape, mode payloads, status reporting, ID hygiene, and the BLOCKED escape hatch shared by every implementer subagent.
data-ai19
parallelize
Use when plan.md is approved and the QRSPI pipeline needs a parallelization plan — analyzes task dependencies and file overlap, decides execution mode, produces parallelization.md with a symbolic branch map; hands off to Implement
testing19
implement
Per-phase implementation orchestrator. In full pipeline mode, resolves symbolic bases from parallelization.md to concrete commits, creates worktrees and stage commits, runs baseline tests, dispatches implementer + reviewer subagents per task per the wave schedule, runs the fix loop, presents the batch gate, and routes to the next route step (typically Integrate). In quick-fix mode, dispatches the single task (or a fix-task batch from fixes/{type}-round-NN/) through the same per-task implementer + reviewer flow, presents the batch gate (with quick-fix-mode menu), and routes to Test.
testing19
research-isolation
Pre-Flight check shared by research-phase agents (specialist, collator, reviewer) that refuses dispatches whose prompt contains goals-content or out-of-scope question content.
development19
plan
Use when prior artifacts are approved and the QRSPI pipeline needs detailed task specs — breaks structure into ordered tasks with test expectations, dependencies, and LOC estimates (full pipeline requires design+structure; quick fix requires only goals+research)
development19
phasing
Use when design.md is approved and the QRSPI pipeline needs vertical slice authoring, phase boundary decisions, roadmap.md authoring, current-phase pruning, and goal-ID consistency validation — sits between Design and Structure
development19
using-qrspi
Use when starting any conversation — establishes the QRSPI pipeline for agentic software development, requiring structured progression through Goals, Questions, Research, Design, Phasing, Structure, Plan, Parallelize, Implement, Integrate, Test, with Replan firing between phases
development19
research-isolation
Pre-Flight check shared by research-phase agents (specialist, collator, reviewer) that refuses dispatches whose prompt contains goals-content or out-of-scope question content.
development19
implementer-protocol
Cross-cutting QRSPI implementer protocol — dispatch shape, mode payloads, status reporting, ID hygiene, and the BLOCKED escape hatch shared by every implementer subagent.
data-ai19
structure
Use when design.md is approved and the QRSPI pipeline needs file/component mapping — maps vertical slices to specific files, interfaces, and component boundaries
testing19
implement
Per-phase implementation orchestrator. In full pipeline mode, resolves symbolic bases from parallelization.md to concrete commits, creates worktrees and stage commits, runs baseline tests, dispatches implementer + reviewer subagents per task per the wave schedule, runs the fix loop, presents the batch gate, and routes to the next route step (typically Integrate). In quick-fix mode, dispatches the single task (or a fix-task batch from fixes/{type}-round-NN/) through the same per-task implementer + reviewer flow, presents the batch gate (with quick-fix-mode menu), and routes to Test.
testing19
skills/prompt-prose-writer
Apply prompt-design rules when authoring or planning prompt-prose deliverables. Detects whether a deliverable IS prompt prose, and only then Reads the rules and applies R1-R7 before drafting. Preloaded by agent files that may author prompt prose.
documentation19
phasing
Use when design.md is approved and the QRSPI pipeline needs vertical slice authoring, phase boundary decisions, roadmap.md authoring, current-phase pruning, and goal-ID consistency validation — sits between Design and Structure
development19
integrate
Use when all current-phase tasks are implemented — merges task branches, runs cross-task integration review, security review, and CI gate
testing19
goals
Use when starting a new QRSPI pipeline run — captures user intent and constraints through interactive dialogue, then synthesizes a problem-framed goals.md
development19
questions
Use when goals.md is approved and the QRSPI pipeline needs research questions generated — produces tagged questions that guide the Research step without leaking goals
development19
integrate-genuine-fixture
--- name: integrate-genuine-fixture --- # Integrate (genuine-integrate fixture) This fixture file lives under `tests/fixtures/u14-genuine-integrate/skills/integrate/SKILL.md`. The skill slug extracted by the slug extractor is `integrate` (the path segment immediately after `skills/`). U14 lint MUST FAIL for this file because `integrate` matches the exclusion list. This fixture locks the intended failure mode: the slug-extraction fix must NOT silently broaden the exclusion to a no-op. A genui
development16
goals-confusable-prefix-fixture
--- name: goals-confusable-prefix-fixture --- # Goals (confusable-prefix fixture) This fixture file lives under `tests/fixtures/u14-worktree-confusable/skills/goals/SKILL.md`. The ancestor directory `u14-worktree-confusable` contains the substring `integrate` as a non-skill directory segment. The skill slug extracted by the slug extractor is `goals` (the path segment immediately after `skills/`), NOT `integrate`. U14 lint MUST PASS for this file because the slug extractor resolves to `goals`
development16