workflow-analysis
Workflow d'Analyse Obligatoire. Use when working with workflow analysis.
npx skills add majiayu000/claude-skill-registry --skill workflow-analysis-thebeardedbearsas-claude-craft --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Workflow d'Analyse Obligatoire This skill enforces mandatory analysis before any code modification. See @REFERENCE.md for detailed documentation. ## Quick Reference ### Before ANY Change 1. **Understand**: Clear objective + acceptance criteria 2. **Analyze**: Read affected files + dependencies 3. **Document**: Files, impacts, risks, approach 4. **Validate**: User approval if medium/high impact 5. **TDD**: Write tests FIRST ### Impact Levels | Impact | Action | |--------|--------| | Low (1 file, < 1h) | Proceed | | Medium (2-5 files, migration) | Validate with user | | High (> 5 files, breaking changes) | Detailed plan required |
- Quick Reference
- Before ANY Change
- Impact Levels
What does the workflow-analysis skill do?
Workflow d'Analyse Obligatoire. Use when working with workflow analysis.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill workflow-analysis-thebeardedbearsas-claude-craft --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.