workflow-strategy

Produces a solution-strategy document with Key Ideas, ADRs, and architectural decisions for Phase 5.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/NestorMonroy/thyrox --skill workflow-strategy-nestormonroy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-strategy
Source: https://github.com/NestorMonroy/thyrox/tree/main/.claude/skills/workflow-strategy
Command: npx skills add https://github.com/NestorMonroy/thyrox --skill workflow-strategy-nestormonroy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? It prevents architecture decisions made without evidence by enforcing a structured research-and-decide phase that turns Phase 1 analysis findings into a documented solution strategy with justified decisions and ADRs. ## Core Features & Use Cases - Structured Strategy Document: Creates a solution-strategy.md from a template with five mandatory sections: Key Ideas, Fundamental Decisions, Technology Stack, Architecture Patterns, and Quality Goals. - Research Before Deciding: Requires listing unknowns, investigating alternatives with pros/cons, and justifying each choice with evidence before committing. - Constraint & ADR Compliance: Verifies decisions against existing ADRs, constitution.md, and Phase 4 constraints, and creates new ADRs for major architectural choices. - Use Case: After completing discovery and constraints analysis for a work package, run this phase to produce skill-activation-solution-strategy.md, present the key decisions at a human gate, and only proceed to planning after explicit approval. ## Quick Start Ask the assistant to start Phase 5 STRATEGY for the active work package and produce the solution-strategy document with Key Ideas and ADRs.

Frequently Asked Questions about workflow-strategy

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

FAQPage Schema
How do I document architectural decisions with ADRs?▼

Create an ADR file in context/decisions/ using the tpl-adr.rst template for each major architectural decision. Each decision entry records alternatives considered, justification, and implications, and is referenced from the solution-strategy document.

What should a solution strategy document contain?▼

A solution strategy contains five mandatory sections: Key Ideas, Fundamental Decisions, Technology Stack, Architecture Patterns, and How We Achieve Quality Goals. It must also show adherence to constraints and traceability back to requirements and analysis findings.

When should I research alternatives before choosing an architecture?▼

Research alternatives whenever the analysis phase surfaces unknowns or assumptions. Document each option with pros and cons, justify the final choice with evidence, and record uninvestigated assumptions as risks rather than deciding blindly.

Does this workflow support designing agentic AI systems?▼

Yes, a dedicated reference covers agentic system design with extra exit criteria: decision mechanism specification, tool scope definition, real HITL protocol, and observability. The template includes a mandatory checklist for agentic work packages.

What happens if the work package scope grows after strategy?▼

A post-strategy size re-evaluation compares scope against the Phase 1 estimate. If the package grew from micro/small to medium/large, phases 6 through 8 are added to the exit conditions before continuing to planning.