thyrox

Organizes project work through a 12-stage workflow from discovery to standardization.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Unstructured work leads to skipped analysis, lost context between sessions, and undocumented decisions. This Skill enforces a disciplined 12-stage project workflow (DISCOVER through STANDARDIZE) where understanding precedes planning and planning precedes execution, with every phase producing traceable artifacts. ## Core Features & Use Cases - 12-Stage Workflow: Guides work packages through DISCOVER, BASELINE, DIAGNOSE, CONSTRAINTS, STRATEGY, SCOPE, DESIGN/SPECIFY, PLAN EXECUTION, PILOT/VALIDATE, IMPLEMENT, TRACK/EVALUATE, and STANDARDIZE, with scalability tiers (micro to large) that skip stages appropriately. - Methodology Skill Integration: Anchors 11 methodology namespaces (PDCA, DMAIC, RUP, PMBOK, BABOK, Lean, PPS, Strategic Planning, Consulting Process, BPA, RM) as sub-processes inside workflow stages. - Artifact & State Management: Defines work package directory structures, naming conventions, YAML metadata rules, decision gates, and session state files (focus.md, now.md) for cross-session continuity. - Use Case: A user asks "how do I organize adding multi-language support to my app?" The Skill starts at DISCOVER, creates a timestamped work package, decomposes the work into traceable tasks [T-NNN] linked to requirements (R-NN), and tracks execution through completion. ## Quick Start Ask the assistant to create a plan for your next feature using the thyrox workflow, starting with the DISCOVER phase.

Frequently Asked Questions about thyrox

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

FAQPage Schema
How do I start a new project with the THYROX workflow?▼

Always start with Phase 1 DISCOVER before planning or writing code. DISCOVER explores context, stakeholders, and symptoms, then creates a timestamped work package directory and a risk register that feed all later phases.

How does THYROX scale phases for small versus large tasks?▼

THYROX defines four size tiers: micro tasks use phases 1, 10, 11; small adds phase 3; medium adds 5, 6, 8; large work packages run all 12 phases. When a methodology flow is active, its anchored stages become non-skippable regardless of size.

What methodology frameworks does THYROX support?▼

THYROX supports 11 methodology namespaces: PDCA, DMAIC, Lean, PPS (Toyota), RUP, RM, PMBOK, BABOK, Strategic Planning, Consulting Process, and BPA. Each methodology skill declares a THYROX Stage anchor and runs as a sub-process inside that workflow stage.

How does THYROX track work across sessions?▼

Session state lives in focus.md and now.md files recording the current work package, phase, and blockers. Each work package stores artifacts in phase-based directories (discover/, plan/, execute/, track/) with YAML metadata including created_at, status, and current_phase.

What is the difference between FASE and Phase in THYROX?▼

FASE N is the global sequential number of a work package in the project, while Phase N is an internal stage of the 12-stage THYROX cycle that resets in each work package. For example, FASE 20 in Phase 10 means work package 20 is currently executing.

When should I not use the full THYROX workflow?▼

Skip the full cycle for micro tasks like quick fixes, which only need phases 1, 10, and 11. The workflow's decision gates and artifact requirements are designed for structured work; forcing them on trivial changes adds overhead without benefit.