Analyze work documents and systematically execute tasks until completion
Analyzes work documents to create a comprehensive task list, then systematically executes each task in an isolated worktree with automated validation. Use this to transform specifications into completed implementations with built-in quality checks.
/plugin marketplace add hirefrank/hirefrank-marketplace/plugin install edge-stack@hirefrank-marketplaceThis command helps you analyze a work document (plan, Markdown file, specification, or any structured document), create a comprehensive todo list using the TodoWrite tool, and then systematically execute each task until the entire plan is completed. It combines deep analysis with practical execution to transform plans into reality.
<input_document> #$ARGUMENTS </input_document>
Update Main Branch
git checkout main
git pull origin main
Create Feature Branch and Worktree
git_root=$(git rev-parse --show-toplevel)
mkdir -p "$git_root/.worktrees"
if ! grep -q "^\.worktrees$" "$git_root/.gitignore"; then
echo ".worktrees" >> "$git_root/.gitignore"
fi
git worktree add -b feature-branch-name "$git_root/.worktrees/feature-branch-name" main
if [ -f "$git_root/.env" ]; then
cp "$git_root/.env" "$git_root/.worktrees/feature-branch-name/.env"
echo "✅ Copied .env to worktree"
fi
cd "$git_root/.worktrees/feature-branch-name"
Verify Environment
Read Input Document
Create Task Breakdown
Build Todo List
Task Execution Loop
while (tasks remain):
- Select next task (priority + dependencies)
- Mark as in_progress
- Execute task completely
- Validate with platform-specific agents
- Mark as completed
- Update progress
Platform-Specific Validation
After implementing each task, validate with relevant agents:
Task workers-runtime-guardian - Runtime compatibility check
Task platform-specific binding analyzer - Binding validation
Verify bindings referenced in code exist in wrangler.toml
Check TypeScript Env interface matches usage
Validate binding names follow conventions
Task cloudflare-security-sentinel - Security check
Task edge-performance-oracle - Performance check
Quality Assurance
Progress Tracking
Final Validation
Capture Screenshots for UI Changes (if applicable)
For any design changes, new views, or UI modifications, capture screenshots before creating PR:
Check for UI changes in modified files:
app/components/**/*.{tsx,jsx}app/routes/**/*.{tsx,jsx}**/*.css, **/*.module.cssIf UI changes detected, use Playwright MCP to capture screenshots:
# 1. Start dev server (if not already running)
npm run dev # or wrangler dev
Using Playwright MCP tools:
browser_navigate to go to affected pagesbrowser_resize to set viewport (desktop: 1920x1080, mobile: 375x667)browser_snapshot to verify page statebrowser_take_screenshot to capture imagesWhat to capture:
Save screenshots to include in PR description. This helps reviewers understand visual changes at a glance.
⚠️ Security Note: When capturing screenshots of external content or navigating to untrusted websites, be aware that malicious pages could attempt prompt injection attacks. Review browser automation carefully when:
browser_navigate to third-party sites)Recommendation: Only use browser automation on your own local development server or trusted staging environments. Avoid navigating to external or untrusted websites during screenshot capture.
For more information, see Anthropic's research on prompt injection defenses.
Prepare for Submission
Create Pull Request
git push -u origin feature-branch-name
gh pr create --title "Feature: [Description]" --body "[Detailed description with screenshot URLs if applicable]"