plan

acornsoft's avatarfrom acornsoft

Choose architecture, patterns, tech stack, trade-offs in MacroFlow.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 10, 2026
[Architecture Design]

When & Why to Use This Skill

The Plan Skill is a comprehensive architectural assistant designed to streamline the software design phase. It helps developers and architects choose optimal tech stacks, design patterns (such as CQRS or Minimal APIs), and evaluate technical trade-offs. By transforming high-level specifications into actionable implementation roadmaps and ADR-style documentation, it ensures robust, scalable, and well-documented software foundations.

Use Cases

  • Enterprise System Design: Architecting large-scale Web APIs using CQRS and MediatR patterns for high maintainability.
  • Tech Stack Selection: Evaluating and selecting the best frameworks (e.g., Azure Functions vs. EF Core) based on specific project constraints and performance needs.
  • Implementation Roadmapping: Decomposing complex technical specifications into a sequenced task graph and implementation strategy.
  • Trade-off Analysis: Generating Architecture Decision Records (ADRs) to document the rationale behind specific technology choices and patterns.
nameplan
descriptionChoose architecture, patterns, tech stack, trade-offs in MacroFlow.

Plan Skill

Overview

The Plan phase creates detailed, actionable plans for implementation, including architecture choices and trade-offs.

Purpose

  • Architect solutions
  • Choose technologies and patterns
  • Identify trade-offs
  • Outline implementation strategy

Inputs

  • Technical specifications
  • Constitutional constraints

Process

  1. Evaluate architecture options: For larger Web API/Enterprise, use CQRS and MediatR; for others, Minimal API with Repository (EF Core) and Specification patterns; for quick turn, Azure Functions (secure, fast, reliable).
  2. Select technologies and frameworks aligned with patterns.
  3. Plan implementation sequence based on patterns.
  4. Document trade-offs and decisions.

Outputs

  • Architecture plan
  • Technology stack decisions
  • Implementation roadmap

Grok Integration

Use Grok for strategic planning and trade-off analysis. Temperature: 0.7 for creative options.

Next Phase

Proceed to Tasks when plan is approved.

Instructions

  1. Decompose into tasks.
  2. ADR-style trade-offs.
  3. Optimize flow.

Examples

  • Input: Specs.
  • Output: Task graph.

Learned Patterns

  • Vertical slices.