Read cycle manifests and draft scope and problem statements for architectural planning.
npx skills add https://github.com/ddpoe/pev-agent-nexus --skill pev-architect
Please help me install this Agent Skill. Skill: pev-architect Source: https://github.com/ddpoe/pev-agent-nexus/tree/main/plugins/pev/skills/pev-architect Command: npx skills add https://github.com/ddpoe/pev-agent-nexus --skill pev-architect
The Skill provides a structured methodology for planning and framing architectural work within a cycle, guiding exploration, boundary setting, and pitch creation to align the Builder and Auditor.
Provide the cycle manifest doc ID and the user request, and I will read the manifest to outline the initial scope and problem framing.
High-intent search queries and answers about installing and using this skill.
Draft an architectural scope by reading the cycle manifest, exploring high-level codebase interfaces, and bounding work at the module level. This produces an early scope and problem write-up that aligns the Builder and Auditor for rapid execution.
Structure a Shape Up–style cycle pitch by outlining the problem, solution sketch, constraints, and module-level boundaries. This approach frames the architectural work and establishes clear scope to guide engagement, user stories, and task generation.
Explore a codebase for architectural boundaries by conducting targeted, high-level exploration of codebase interfaces. This bounds the work effectively by assessing module-level boundaries rather than per-function changes, keeping the focus on structural scope.
Iteratively update a cycle manifest across rounds by preserving context and supporting NEEDS_INPUT interactions. This allows you to gather user direction, refine the problem framing, and maintain alignment throughout the planning phase workflow.
Architectural planning for a cycle does not require per-function change assessments. It emphasizes module-level boundaries and high-level interface exploration to bound work, deliberately avoiding implementation details to maintain structural focus.
Prerequisites for architectural cycle planning include providing a cycle manifest document ID and the user request. The Skill reads the manifest to outline initial scope, requiring no additional dependencies or component installations to begin framing work.
adiomasCoordinate independent tasks in parallel using isolated git worktrees.
nahisahoAnalyze proposed changes to detect breaking changes and generate impact reports.
1molchuanConvert user requirements into a formal constraint set during RPI Research.
ralvarezdevGuide design-level refactoring to improve module boundaries and encapsulation.
