thyrox

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

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/jcg-admin/IACT-ui --skill thyrox-jcg-admin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: thyrox
Source: https://github.com/jcg-admin/IACT-ui/tree/main/.claude/skills/thyrox
Command: npx skills add https://github.com/jcg-admin/IACT-ui --skill thyrox-jcg-admin

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 decisions, and untracked progress. THYROX provides a disciplined 12-stage cycle (DISCOVER through STANDARDIZE) that turns any work item — features, bug fixes, refactoring, documentation, or research — into a tracked work package with artifacts, gates, and traceability. ## Core Features & Use Cases - 12-Stage Workflow: Each stage (DISCOVER, BASELINE, DIAGNOSE, CONSTRAINTS, STRATEGY, SCOPE, DESIGN/SPECIFY, PLAN EXECUTION, PILOT/VALIDATE, IMPLEMENT, TRACK/EVALUATE, STANDARDIZE) produces artifacts that feed the next, with human decision gates between stages. - Scalable by Work Size: Micro tasks use only stages 1, 10, 11; large projects run the full cycle, so overhead matches risk. - Methodology Plugins: Anchors 11 frameworks (PDCA, DMAIC, Lean, RUP, PMBOK, BABOK, PPS, Strategic Planning, Consulting Process, BPA, Requirements Management) inside the appropriate stages. - Use Case: A user asks "descompón la migración multi-idioma en tareas" — the skill creates a timestamped work package, decomposes work into traceable tasks [T-NNN] linked to requirements, and tracks execution in a task plan. ## Quick Start Ask the assistant to create a plan for your next feature using the thyrox workflow, starting with the DISCOVER stage.

Frequently Asked Questions about thyrox

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

FAQPage Schema
How do I plan a project using a structured workflow?▼

Start with the DISCOVER stage to explore context, stakeholders, and symptoms before planning. THYROX then guides work through analysis, strategy, scoping, decomposition, and execution stages, each producing artifacts that feed the next.

How do I break a feature into trackable tasks?▼

Use the PLAN EXECUTION stage (decompose) to create atomic tasks with IDs like [T-NNN], each traced back to a requirement (R-N). The task plan includes a dependency graph and lives in the work package directory.

When should I skip stages in the THYROX workflow?▼

Stage count scales with work size: micro fixes use stages 1, 10, 11; small features add stage 3; medium work adds strategy and decomposition; only large multi-session projects run all 12 stages.

Which methodology should I use: DMAIC, Lean, or PDCA?▼

Use DMAIC for reducing defects with statistical data, Lean for eliminating visible waste like time and inventory, and PDCA for fast iterative improvement cycles. The methodology-selection-guide reference provides decision trees for similar candidates.

Where are work package artifacts stored?▼

Artifacts live in timestamped directories under context/work/YYYY-MM-DD-HH-MM-SS-name/, with flat phase-based subfolders (discover/, analyze/, plan/, execute/, track/) containing markdown files with YAML metadata blocks.

Why should background bash tasks not combine redirection with polling loops?▼

Combining run_in_background with output redirection empties the task output file, causing manual polling loops to run forever as zombie processes. Use notification-driven completion or synchronous execution with a hard timeout instead.