Evaluate design decisions using BLUEPRINT.md and PLAN.md without modifying code.
npx skills add https://github.com/whatwecando/tombola --skill forge-discuss
Please help me install this Agent Skill. Skill: forge-discuss Source: https://github.com/whatwecando/tombola/tree/main/.claude/skills/forge-discuss Command: npx skills add https://github.com/whatwecando/tombola --skill forge-discuss
Architecture discussion mode enables teams to explore and debate design decisions without modifying the codebase, helping reduce risk and align stakeholders before implementation.
Initiate architecture discussion mode by reviewing BLUEPRINT.md, PLAN.md, and the current codebase structure, then discuss the topic and propose approaches.
High-intent search queries and answers about installing and using this skill.
To evaluate architecture design decisions without modifying the codebase, reference your BLUEPRINT.md, PLAN.md, and codebase structure to ground discussions and prevent accidental code changes during design reviews.
Yes, you can plan a refactoring strategy by exploring trade-offs first. Structured architectural discussions evaluate design constraints and align stakeholders on implementation approaches before any code changes are made.
Yes, you need BLUEPRINT.md and PLAN.md files to start a design review discussion. The skill requires access to these files and the current codebase structure to ground architectural decisions and prevent scope creep.
The best way to align stakeholders on new software architecture approaches is facilitating structured discussions around system design and constraints. This reduces risk by debating approaches using existing blueprints before implementation.
Grounding architecture discussions in existing plans prevents scope creep by referencing BLUEPRINT.md and PLAN.md files. This ensures proposed design decisions and refactoring strategies remain anchored to the original system constraints and goals.
You should avoid using discussion mode for codebase refactoring when you actually need to implement changes. This mode strictly evaluates design decisions and proposes approaches without modifying any code in the current codebase structure.
phillip-hirschIdentify refactoring opportunities to transform shallow modules into deep ones.
northseadlGenerates bite-sized implementation plans for software development tasks in Tled documents.
TECHKNOWMAD-LABSValidate code against specifications and analyze quality with severity reports.
speednet-softwareDetect KISS principle violations in codebases and suggest refactoring recommendations.
