Generate research documentation and coordinate adversarial plan reviews for GitHub issues.
npx skills add https://github.com/psaab/xpf --skill research-psaab
Please help me install this Agent Skill. Skill: research Source: https://github.com/psaab/xpf/tree/main/.claude/skills/research Command: npx skills add https://github.com/psaab/xpf --skill research-psaab
This skill prevents the high cost of throwaway code by enforcing a rigorous, multi-perspective architectural review process before any implementation begins.
Invoke the research skill by providing the issue number and a brief description to initiate the adversarial review process for your proposed architectural change.
High-intent search queries and answers about installing and using this skill.
You validate architectural soundness by running an adversarial 3-way plan review process that stress-tests design proposals across multiple perspectives before implementation begins. This prevents the high cost of throwaway code by coordinating feedback to reach a converged, manually approved plan.
An adversarial plan review is a structured process that generates detailed research documentation on a dedicated branch and iterates through feedback rounds. It validates design tradeoffs and technical feasibility by coordinating hostile feedback from multiple tools until a converged plan-of-action is reached.
You start a 3-way architectural code review by invoking the process with your GitHub issue number and a brief description. The system then initiates the adversarial review process, generating research documentation on a dedicated branch and iterating through feedback rounds.
Yes, the structured plan review requires integration with Claude SMR, Codex, and AGY to validate design tradeoffs and technical feasibility. These tools coordinate to provide the triple-review validation needed to stress-test your architectural design proposals.
No, the architectural review process does not modify production source code. It operates as a safety gate by generating research documentation on a dedicated branch, ensuring no production code is touched until a plan reaches a converged PLAN-READY state with explicit manual approval.
You should use a multi-perspective architectural review process when proposing complex architectural changes to GitHub tracking issues. It is designed to enforce rigorous validation of design tradeoffs before implementation, preventing the high cost of throwaway code in software engineering projects.
snake-dev-teamAutomate adversarial code review and quality assurance for codebases.
HellblazerDelegate plan-approved Java implementation tasks to the java-developer agent.
samChang72Coordinate multi-phase research with Claude, Codex, and agy AI models.
igor1309Review architecture specifications for completeness, abstraction, and separation of concerns.
