solution-architect-agent

Generates codebase-grounded implementation plans with options, risks, and file-level impact mapping.

3|1|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/PALabs-v1/AI_friend --skill solution-architect-agent-palabs-v1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: solution-architect-agent
Source: https://github.com/PALabs-v1/AI_friend/tree/main/skills/solution-architect-agent
Command: npx skills add https://github.com/PALabs-v1/AI_friend --skill solution-architect-agent-palabs-v1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Non-trivial code changes often fail because implementation starts before anyone maps affected files, compares approaches, or surfaces hidden risks. This Skill enforces a discovery-first planning workflow so every refactor, feature, or reliability fix begins with a concrete, repository-grounded plan instead of assumptions. ## Core Features & Use Cases - Discovery-First Workflow: Inspects root docs, architecture documentation, agent context files, and affected modules before proposing anything. - Structured Output Contract: Produces a six-section plan covering problem statement, affected files, at least two options with trade-offs, a justified recommendation, a numbered implementation plan, and risks. - Planning-Only Discipline: Explicitly avoids writing code, premature abstraction, and single-solution bias. - Use Case: Before refactoring a cross-module authentication flow, run this Skill to map every touched file, compare two migration strategies, and get an ordered step list with rollback risks called out. ## Quick Start Ask the agent to plan the implementation of your feature or refactor before writing any code, and it will return a structured plan grounded in your repository.

Frequently Asked Questions about solution-architect-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a code implementation before writing code?▼

Invoke this Skill with a description of the change you want. It first inspects your repository's docs, architecture files, and affected modules, then returns a structured plan with options, a recommendation, ordered steps, and risks.

What should an implementation plan for a refactor include?▼

A solid plan includes a problem statement, affected files and dependencies, at least two compared options with trade-offs, a justified recommendation, a numbered step sequence with file paths, and a list of risks and open questions.

Does this Skill write the actual code changes?▼

No. This Skill is planning-only by design. It produces the implementation plan, file-level impact mapping, and risk analysis, but deliberately avoids generating implementation code during the planning phase.

When should I use architecture planning versus coding directly?▼

Use planning for non-trivial work: multi-file changes, refactors, reliability fixes, or behavior updates with rollback risk. Trivial single-file edits with obvious solutions do not benefit from a full planning pass.

Why does the plan require comparing at least two options?▼

Comparing options prevents jumping to the first plausible solution. Each option is evaluated on complexity, breakage risk, performance, maintainability, and fit with existing repository conventions before one is recommended.