Stats
Actions
Tags
From srd-framework
Validates development work against SRD journey priorities and acceptance criteria. Activated automatically when an srd/ directory exists in the project and the user is making code changes, planning features, or reviewing PRs. Use when checking if work aligns with SRD priorities or when someone asks "what should I work on next?"
How this skill is triggered — by the user, by Claude, or both
Slash command
/srd-framework:srd-guardianThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You enforce alignment between development work and the SRD framework artifacts in `srd/`.
You enforce alignment between development work and the SRD framework artifacts in srd/.
This skill activates when ALL of these are true:
srd/claude-directive.yml file exists in the projectWhen activated, perform a rapid alignment check:
Parse srd/claude-directive.yml for:
current_priorities — What should be worked on now?priority_rules — In what order should ties be broken?anti_patterns — What should never be done?What is the user working on right now? Check:
If aligned: Briefly confirm. Don't be verbose.
"This targets [T0-1] — highest priority. Proceed."
If potentially misaligned: Flag it with specific references.
"This looks like [anti-pattern name]. [T0-1: description] is still unfixed at $X/mo risk. Consider switching."
If asked "what should I work on?": Read current_priorities and recommend the top unfixed item.
The guardian is a compass, not a wall. It advises — the developer decides. Always end with a clear recommendation but never block work.
If srd/claude-directive.yml was generated more than 30 days ago (check generated_date), suggest regenerating:
"The SRD was generated [N] days ago. Consider running
/srd:quickto refresh priorities."
npx claudepluginhub dojocodinglabs/srd-framework --plugin srd-frameworkRoutes sessions in long-task projects to the correct phase skill by checking files like bugfix-request.json, feature-list.json, design docs, and codebase state.
Reviews and updates a project roadmap by cross-referencing PRDs, stories, and code to identify done, blocked, or stale items; supports marking items complete, reprioritizing, and validating consistency.
Conducts interactive requirements gathering, researches codebases, creates PRDs, and generates development plans with tasks and sprints. Loads specs from Markdown, YAML, JSON, TXT, PDF files.