sf-architect-solutioning

Architect Salesforce solutions with declarative-first patterns and pre-implementation documentation gates.

Updated Aug 27, 2026

Search Tags:#architecture #best practices #documentation #salesforce #solutioning #technical architect

Ready to run

npx skills add https://github.com/Mar5929/claude-toolkit --skill sf-architect-solutioning

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sf-architect-solutioning
Source: https://github.com/Mar5929/claude-toolkit/tree/main/config/skills/sf-architect-solutioning
Command: npx skills add https://github.com/Mar5929/claude-toolkit --skill sf-architect-solutioning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that Salesforce solutions are architected with best practices, proper documentation, and adherence to architectural principles before any code is written, preventing technical debt and ensuring maintainability.

Core Features & Use Cases

Requirement Clarification: Pushes back on vague requirements and interviews users for necessary details.
Pre-Implementation Gate: Verifies that all living documents (BRD, Technical Spec, Data Model, Component Registry) are up-to-date before development.
Solution Planning: Develops structured solution plans, including component identification, pattern mapping, and risk assessment.
Use Case: When a stakeholder asks to "build a new customer portal," this Skill will guide them through clarifying requirements, ensuring existing documentation is updated, and presenting a detailed architectural plan before any development begins.

Quick Start

Use the sf-architect-solutioning skill to architect a new feature for the customer portal.

Frequently Asked Questions about sf-architect-solutioning

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

FAQPage Schema

How do I architect a Salesforce solution before writing any code?▼

To architect a Salesforce solution properly, you should clarify requirements, update living documents like BRDs and technical specs, and map components to architectural patterns. This approach enforces a declarative-first mindset, ensuring maintainability and preventing technical debt before development begins.

What is a pre-implementation gate in Salesforce solutioning?▼

A pre-implementation gate in Salesforce solutioning is a rigorous checkpoint that verifies all living documents—including the BRD, Technical Spec, Data Model, and Component Registry—are current and complete. This ensures architectural alignment and prevents premature development.

How do I stop vague Salesforce requirements from causing technical debt?▼

To stop vague Salesforce requirements from causing technical debt, interview stakeholders to extract necessary details and push back on unclear requests. Establishing comprehensive documentation and adhering to architectural patterns ensures solutions are built with expert rigor.

Can I use a declarative-first approach for complex Salesforce features like a customer portal?▼

Yes, a declarative-first approach is recommended for complex Salesforce features like a customer portal. By identifying standard components, mapping architectural patterns, and assessing risks before development, you ensure the solution leverages native capabilities effectively.

What living documents need to be updated before Salesforce development starts?▼

Before Salesforce development starts, living documents that need to be updated include the Business Requirements Document (BRD), Technical Specification, Data Model, and Component Registry. Verifying these documents are complete prevents architectural misalignment.

When should I not use standard architectural patterns for Salesforce solutioning?▼

You should reconsider standard architectural patterns for Salesforce solutioning when stakeholder requirements remain vague or existing living documents are outdated. Proceeding without a rigorous pre-implementation gate and complete documentation risks introducing technical debt.