Manage approval, execution, review, and verification boundaries for software implementation workflows.
npx skills add https://github.com/OrestesK/pi --skill manager-workflow
Please help me install this Agent Skill. Skill: manager-workflow Source: https://github.com/OrestesK/pi/tree/main/skills/manager-workflow Command: npx skills add https://github.com/OrestesK/pi --skill manager-workflow
This Skill prevents uncontrolled implementation work by establishing clear approval boundaries, staged execution, progress tracking, review, and final verification for material changes.
Use the manager workflow to plan, approve, implement, review, and verify the requested repository change within explicit behavioral boundaries.
High-intent search queries and answers about installing and using this skill.
Implementation scope control is managed by defining non-goals, establishing stop conditions, and obtaining approval before any repository mutation begins. This prevents uncontrolled implementation work on complex features or refactors.
An approval workflow for software implementation planning is a staged process requiring decision-ready proposals and explicit authorization before execution. It ensures material changes undergo reviewable planning and evidence-based completion.
Code review and verification are coordinated by routing work through planning, implementation, independent review, fixes, and final read-only verification. This preserves continuity and tracks evidence for repository migrations.
Yes, this workflow applies to debugging, testing, architecture changes, refactors, and service modifications. It coordinates these tasks by requiring bounded implementation ownership and protected-action authorization.
Stage coordination is needed for feature development when work requires reviewable planning, evidence-based completion, and protected behavioral boundaries. It manages work from proposal approval through final verification.
Asynchronous review requires focused evidence and decision-ready proposals to function effectively. The workflow stops when material decisions remain unresolved or when canonical owners cannot be identified for protected actions.
harkersDecompose goals into bounded work units with scope, sequencing, and acceptance criteria.
azat-ioExecute approved implementation plans with step-by-step verification and checkpoints.
GrinRusDefine and enforce shared output, read, and loop-safety policies across AIDD stages.
nahisahoDefine QA strategy, test plans, and quality metrics for software projects.
