jimiryquai/pi-agent/work

Work Plan Execution Command

Execute a work plan efficiently while maintaining quality and finishing features.

Introduction

This command takes a work document (plan, specification, or todo file) and executes it systematically. The focus is on shipping complete features by understanding requirements quickly, following existing patterns, and maintaining quality throughout.

Input Document

<input_document> #$ARGUMENTS </input_document>

Execution Workflow

Phase 1: Orchestration and Tasking

1. Assign Persona: The tdm (Technical Delivery Manager) expert handles this phase.
2. Setup Environment:

• Branching: Check/Create the feature branch.
• Worktrees: Use the git-worktree skill to create isolated environments for each parallel expert if needed.
• Parallel Panes: Use the spawn_team tool to open separate Zellij panes for the required engineers, pointing each to their respective worktree cwd if applicable.

1. Create Todo List:

• Break the plan into units.
• Assign data and API units to the backend-engineer.
• Assign UI and design units to the frontend-engineer.
• Assign verification and integration testing to the tester.

Phase 2: Execute in Parallel

1. Backend & Frontend Collaboration:

• The backend-engineer implements core logic and APIs.
• The frontend-engineer builds the UI following project design standards.
• Both work autonomously in their own Zellij panes.

1. High-Fidelity Testing:

• The tester writes integration tests (Real > Fake > Mock).
• The tester verifies both Backend logic and Frontend visual/UX integrity.

Phase 3: Finish and Ship

1. Final Quality Check:

• Full test suite run.
• Linting check.
• Verification against requirements.

1. Ship it:

• Squash/Commit with conventional messages.
• Create PR with visual evidence (screenshots for UI).
• Cleanup: Remove temporary worktrees if used.

Phase 4: Next Steps

• Document Learning: Run /compound to capture the solution for future reference.