Develop and iteratively refine software implementation plans through structured review cycles.
npx skills add https://github.com/ahrav/Gossip-rs --skill plan-forge
Please help me install this Agent Skill. Skill: plan-forge Source: https://github.com/ahrav/Gossip-rs/tree/main/.claude/skills/plan-forge Command: npx skills add https://github.com/ahrav/Gossip-rs --skill plan-forge
This Skill addresses the common issue of creating flawed implementation plans that lead to costly mistakes during software development by introducing a rigorous, iterative review and revision process.
Use the plan-forge skill to create an implementation plan for adding a new retry mechanism to the API client.
High-intent search queries and answers about installing and using this skill.
Iterative implementation plan creation uses a structured review-and-revise cycle to stress-test architectural decisions against codebase realities. This process catches incorrect assumptions, unnecessary complexity, and performance pitfalls before development begins.
Stress-testing a software design involves analyzing proposed solutions across correctness, footguns, simplification, and performance. A multi-agent approach provides comprehensive analysis to ensure the implementation strategy is sound and well-vetted.
Refining a software implementation plan requires generating an initial strategy and applying multiple rounds of structured review and revision. This iterative development process mitigates risks by identifying flaws in the proposed architecture.
Yes, a multi-agent approach reviews codebase assumptions by evaluating the implementation strategy across multiple dimensions. It identifies incorrect assumptions and potential footguns, ensuring the plan accounts for codebase realities.
Iterative plan creation is needed before implementing complex new features that touch critical system components. It ensures the implementation strategy is robust, mitigates development risks, and verifies architectural decisions.
Without iterative revision, an initial software design risks containing flawed architectural decisions, unnecessary complexity, and performance pitfalls. Stress-testing proposed solutions against codebase realities is necessary to avoid costly mistakes during development.
morodomiGenerate a TDD implementation plan and Test List in Cycle documentation.
makerjackieExecute implementation plans in structured batches with git worktrees.
Cogni-DAOReview code changes for correctness, style, and edge cases against specifications.
mntheAutomate code consistency checks against project standards during verification and planning.
