pi-dynamax-feature-workflow

Coordinate feature development from discovery through testing and completion evidence.

Updated Jul 17, 2026

Search Tags:#feature development #workflow orchestration #test-driven development #specialist review #adversarial validation #graphify #dynamax

Ready to run

npx skills add https://github.com/dymayday/pi-dynamax-feature-workflow --skill pi-dynamax-feature-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pi-dynamax-feature-workflow
Source: https://github.com/dymayday/pi-dynamax-feature-workflow/tree/main
Command: npx skills add https://github.com/dymayday/pi-dynamax-feature-workflow --skill pi-dynamax-feature-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents feature work from becoming an unstructured sequence of guesses by coordinating discovery, architecture context, specialist review, implementation, testing, and completion evidence.

Core Features & Use Cases

Structured Feature Discovery: Guides requirements exploration, question prioritization, specification drafting, and approval.
Specialist Review and Adversarial Challenge: Uses relevant enabled skills, Graphify context, bounded fanout, retries, and evidence-based adjudication to identify material risks.
Test-Driven Delivery: Coordinates implementation planning, TDD, focused validation, final verification, and branch completion for new or cross-cutting features.
Use Case: Use it to build a feature that spans multiple modules and requires architectural decisions, specialist input, tests, review, and documented completion evidence.

Quick Start

Ask the Pi agent to use this skill to build a described feature, optionally including the standalone word autopilot for routine reversible decisions.

Frequently Asked Questions about pi-dynamax-feature-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I structure feature development to include specialist review and test-driven delivery?▼

You can prevent unstructured feature development guesswork by coordinating discovery, architecture context, specialist review, test-driven implementation, and completion evidence. Structured feature development ensures cross-cutting features undergo adversarial validation before branch completion.

What is adversarial validation in the context of cross-cutting feature implementation?▼

Adversarial validation in feature implementation uses enabled skills, Graphify context, bounded fanout, and retries to identify material risks. This evidence-based adjudication process challenges architectural decisions during specialist review.

When do I need workflow orchestration for new feature development?▼

Workflow orchestration is needed for new feature development when there are meaningful product decisions, architectural risk, unclear dependencies, or a need for adversarial review. It coordinates structured discovery through final verification.

Do I need Pi and Dynamax to orchestrate test-driven development workflows?▼

Yes, orchestrating test-driven development workflows requires Pi with the Dynamax workflow tool and relevant supporting Agent Skills. These dependencies manage worktrees, Graphify, brainstorming, planning, verification, and branch completion.

Can I automate routine decisions during feature workflow orchestration?▼

Yes, you can automate routine decisions during feature workflow orchestration by including the standalone word autopilot in your request. The Pi agent handles reversible decisions automatically while maintaining the structured workflow.

What is the best way to document completion evidence for cross-cutting features?▼

The best way to document completion evidence for cross-cutting features is through a structured workflow that coordinates final verification and branch completion. This ensures all architectural decisions and specialist reviews are validated.