Add integration/E2E tests to existing codebase using Design Docs
fitchmultz/pi-workflows
SkillsMP has collected 60 skills from fitchmultz/pi-workflows. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 60
- GitHub stars
- 1
- GitHub forks
- 0
Skills in this repository
Showing 40 of 60 collected skills.
Execute materialized task files in autonomous execution mode
Execute from codebase-scoped analysis through optional ADR decisions to complete Design Doc approval
Investigate problem, verify findings, and derive solutions
Adjust an already-implemented UI in-session with verification against the design source
Execute materialized frontend task files in autonomous execution mode
Execute from repository evidence through applicable UI Spec and optional ADR decisions to complete frontend Design Doc approval
Create frontend work plan from design document and obtain plan approval
Design Doc compliance and security validation with optional auto-fixes
Execute materialized fullstack task files with layer-aware agent routing
Orchestrate full-cycle implementation across backend and frontend layers
Orchestrate the complete implementation lifecycle from requirements to deployment
Create work plan from design document and obtain plan approval
Generate PRD and Design Docs from existing codebase through discovery, generation, verification, and review workflow
Design Doc compliance and security validation with optional auto-fixes
Execute tasks following appropriate rules with rule-advisor metacognition
Update existing design documents (Design Doc / PRD / ADR) with review
Applies language-agnostic and backend technical decision criteria, anti-pattern detection, debugging, and quality gates. Use when reviewing general/backend implementation choices, code smells, failures, or implementation completeness.
Determines which of PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires, and where each is stored. Use when deciding documentation scope, or when creating or reviewing a technical document.
Records where resources outside the repository live (design source, design system, API schema, IaC source, secret store) and how design, implementation, and verification reach them. Use when work depends on an external resource, or when the user mentions…
Applies React/TypeScript-specific technical decision criteria, anti-pattern detection, debugging, and frontend quality gates. Use when reviewing components, hooks, browser behavior, or frontend implementation completeness.
Implementation strategy selection framework. Use when planning implementation strategy, selecting development approach, or defining verification criteria.
Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from structure. Use when a requirement enters a workflow, before design begins.
Guides subagent coordination through implementation workflows. Use when orchestrating multiple agents, managing workflow phases, or determining autonomous execution mode.
Implements React/TypeScript unit, integration, and browser E2E tests with the repository's configured runner, mocks, setup, and browser harness. Use when creating or completing frontend tests and generated test skeletons.
Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from structure. Use when a requirement enters a workflow, before design begins.
Add integration/E2E tests to existing codebase using Design Docs
Execute materialized task files in autonomous execution mode
Execute from codebase-scoped analysis through optional ADR decisions to complete Design Doc approval
Investigate problem, verify findings, and derive solutions
Adjust an already-implemented UI in-session with verification against the design source
Execute materialized frontend task files in autonomous execution mode
Execute from repository evidence through applicable UI Spec and optional ADR decisions to complete frontend Design Doc approval
Create frontend work plan from design document and obtain plan approval
Design Doc compliance and security validation with optional auto-fixes
Execute materialized fullstack task files with layer-aware agent routing
Orchestrate full-cycle implementation across backend and frontend layers
Orchestrate the complete implementation lifecycle from requirements to deployment
Create work plan from design document and obtain plan approval
Generate PRD and Design Docs from existing codebase through discovery, generation, verification, and review workflow