workflow-standardize

Documents reusable patterns and closes work packages by updating project guidelines and ADRs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Work packages often end without capturing what was learned, so each new package repeats the same mistakes and rediscovers the same solutions. This Skill runs Phase 12 STANDARDIZE of the THYROX workflow, converting lessons learned into documented reusable patterns and formally closing the work package. ## Core Features & Use Cases - Pattern extraction: Reviews Phase 11 lessons-learned artifacts and converts them into named, structured patterns using the patterns.md template. - System propagation: Updates project guidelines, other workflow skills, and ADRs so improvements persist beyond the current work package. - Formal WP closure: Updates state files (now.md, focus.md, project-state.md), runs validation gates, and produces the final report with baseline-vs-result metrics. - Use Case: After finishing a work package that introduced a new testing convention, run Phase 12 to document the pattern, update the relevant guidelines, mark the phase complete in ROADMAP.md, and close the session with a standardized commit. ## Quick Start Ask the assistant to run Phase 12 STANDARDIZE for the active work package and propagate its lessons learned to the project guidelines.

Frequently Asked Questions about workflow-standardize

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

FAQPage Schema
How do I close a work package and document reusable patterns?▼

Run Phase 12 STANDARDIZE: review the lessons-learned artifact from Phase 11, extract named patterns into patterns.md using the provided template, update guidelines and ADRs, then execute the close-wp script and validation gate to finalize the work package.

What artifacts does the standardize phase produce?▼

It produces a required patterns.md file documenting adopted patterns, guideline and skill updates, and optionally a final-report.md comparing baseline metrics against results. It also updates ROADMAP.md and the session state files now.md, focus.md, and project-state.md.

When should I skip the standardize phase?▼

Skip it for isolated bug fixes without structural impact or minor documentation changes, per the methodology reference. Use it whenever the work package introduced architectural decisions, repeatable code patterns, or measurable success metrics.

What makes a lesson learned qualify as a pattern?▼

A pattern needs a memorable name, a defined context and problem, a concrete solution structure, and known consequences including trade-offs. If the solution cannot be named or only applies to one situation, it is not yet a pattern.

Does the standardize workflow require human approval before closing?▼

Yes, it includes a human gate: the list of patterns and system updates must be presented and explicitly confirmed before executing the work package closure, state file updates, and the final chore(standardize) commit.