architecture-planner

Outline SaaS architecture plans with components, data flows, and tradeoffs.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/internalforces/saas-generic-skills --skill architecture-planner-internalforces
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-planner
Source: https://github.com/internalforces/saas-generic-skills/tree/main/skills/architecture-planner
Command: npx skills add https://github.com/internalforces/saas-generic-skills --skill architecture-planner-internalforces

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architects and product teams need a clear, actionable plan that translates scope into a concrete technical blueprint, reducing rework and misalignment.

Core Features & Use Cases

  • High-level architecture summary that highlights core components and their interactions.
  • Data flow maps that show how data traverses the system from ingestion to storage and dashboards.
  • Tradeoff analysis that compares viable design options and aligns with constraints.

Quick Start

Draft a high-level architecture plan for the requested SaaS feature, including core components, data flows, interfaces, and tradeoffs.

Frequently Asked Questions about architecture-planner

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

FAQPage Schema
How do I plan a SaaS architecture for a new product feature?

To plan a SaaS architecture, outline a focused blueprint covering the architecture summary, main components, data model, data flows, external integrations, and operational concerns. This translates defined scope and workflows into a concrete technical plan.

What is the best way to map data flows for a SaaS application?

Mapping data flows for a SaaS application involves documenting how data traverses the system from ingestion to storage and dashboards. A structured architecture plan identifies these pathways to reduce misalignment and rework.

How do I analyze architecture tradeoffs for moderate scale SaaS systems?

Analyzing architecture tradeoffs for moderate scale SaaS systems requires comparing viable design options against your specific constraints. A focused architecture plan highlights these tradeoffs to align technical decisions with project scope.

Can I use an architecture planner for major features instead of whole products?

Yes, you can use an architecture planner for major features. It applies to projects with defined scope, typical workflows, and moderate scale constraints, producing a recommended implementation sequence for that specific feature.

What should be included in a SaaS architecture blueprint?

A SaaS architecture blueprint should include an architecture summary, core components, data model outline, data flows, external integrations, operational concerns, tradeoffs, and a recommended implementation sequence to guide development.

When do I need a formal SaaS architecture plan?

You need a formal SaaS architecture plan when translating product scope into a technical blueprint for projects with moderate scale constraints. It reduces rework by providing actionable steps for components and data flows.