How does it decide between simple and complex workflows?

It uses a complexity assessment protocol to determine if a task affects a single module or requires multi-module decomposition and dependency-based execution ordering.

Why is architecture context loaded before the codebase exploration?

Loading pre-computed architecture data allows the skill to make reasoning-based decisions about module placement without needing to scan every file, improving speed and accuracy.

What is the primary purpose of the Phase 2 Outline skill?

It creates a detailed technical roadmap for a coding task, ensuring all changes align with the project's specific architecture, package structure, and testing standards.

Does this skill handle testing plans automatically?

Yes, it checks the project's test infrastructure and automatically adds testing profiles to deliverables or creates separate integration test (IT) tasks when required.

Architecture-Driven Solution Outlining

Name: Architecture-Driven Solution Outlining
Author: cuioss

bycuioss

Productivity & Workflow

Generates structured solution outlines by performing intelligent module selection and architecture-driven semantic analysis.

About

The Phase 2 Outline skill serves as the blueprinting engine for the Plan Marshall orchestration layer. It transforms high-level requirements into detailed, executable plans by analyzing pre-computed project architecture. By evaluating module responsibilities and package structures, it determines whether a task requires a simple or complex workflow, ensures code is placed in the correct domain, and automatically includes necessary testing profiles and integration test deliverables to maintain codebase integrity.

Key Features

Dependency-aware ordering for complex, multi-layered solutions
0 GitHub stars
Extensible protocol for domain-specific discovery and assessment
Semantic module and package selection based on architecture context
Standardized deliverable templates with implementation and testing profiles
Automated complexity assessment for single vs. multi-module tasks

Use Cases

Mapping out integration testing requirements for cross-cutting API or UI changes
Ensuring new code placement follows established architectural patterns and package hierarchies
Decomposing a high-level feature request into specific, module-targeted deliverables

About

Key Features

Dependency-aware ordering for complex, multi-layered solutions
0 GitHub stars
Extensible protocol for domain-specific discovery and assessment
Semantic module and package selection based on architecture context
Standardized deliverable templates with implementation and testing profiles
Automated complexity assessment for single vs. multi-module tasks

Use Cases

Mapping out integration testing requirements for cross-cutting API or UI changes
Ensuring new code placement follows established architectural patterns and package hierarchies
Decomposing a high-level feature request into specific, module-targeted deliverables