ryan-mahoney/specops-orchestrate-analysis
skills/specops-orchestrate-analysis/SKILL.md
This skill should be used when the user asks to orchestrate SpecOps analysis from an initial plan output across all targets using sequential subagents.
data-ai
Updated Apr 28, 2026
$ install --global
skillsauthnpx skillsauth add ryan-mahoney/ryan-llm-skills specops-orchestrate-analysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 28, 2026, 8:46 AM136.7s1 file scanned
SKILL.md
- name:
- specops-orchestrate-analysis
- description:
- This skill should be used when the user asks to orchestrate SpecOps analysis from an initial plan output across all targets using sequential subagents.
- disable-model-invocation:
- true
- argument-hint:
- [initial-plan-file-or-scope]
SpecOps Orchestrate Analysis
You are an orchestrator. Execute a SpecOps analysis pipeline from an initial-plan artifact using sequential subagents.
Primary objective:
- Use the output of
specops-initial-planas the source of truth for target decomposition. - For each target, run an analysis subagent.
- Ensure per-target analysis outputs are produced consistently and verified before moving to the next target.
Do not generate specs. Do not implement product code directly unless subagents are unavailable.
Inputs
- Initial plan artifact:
$ARGUMENTS(or infer from user request/repo context). - Related standards/conventions files if present (for example
AGENTS.md,docs/engineering-standards.md).
Before Starting
- Read the initial-plan artifact fully.
- Extract a deterministic, ordered target list. Each target should include:
- Target/module name.
- Scope description.
- Source evidence/files when present.
- Intended analysis output path.
- If output paths are absent, default to:
- Analysis:
docs/specops/analysis/<target-slug>.md
- Announce ordered execution plan before delegating.
Execution Model: Sequential Subagents Per Target
Process one target at a time. Do not parallelize targets.
For each target, run an analysis subagent (use specops-analysis behavior).
Subagent Invocation Template
Agent(
subagent_type: "general-purpose",
description: "SpecOps target <target-slug> - analysis",
prompt: "<PHASE_PROMPT>"
)
PHASE_PROMPT (Analysis)
You are executing SpecOps analysis for one target.
Target: <target-name>
Scope: <target-scope>
Evidence/files: <file-list>
Output file: <analysis-output-file>
Follow the workflow and quality bar from skills/specops-analysis/SKILL.md.
Write the full analysis to <analysis-output-file>.
Do not generate a spec. Do not implement code.
Return: summary, file written, assumptions, risks.
Verification After Each Subagent
After each analysis:
- Confirm output file exists and is non-empty.
- Confirm required sections from
specops-analysisare present. - Confirm claims are evidence-based and assumptions are labeled.
- If invalid/incomplete, run one fix-up subagent for that same target.
Allow up to 2 fix-up attempts per target. If still failing, stop and report blockers.
Fix-Up Subagent Template
Agent(
subagent_type: "general-purpose",
description: "Fix SpecOps <target-slug> analysis",
prompt: "Previous analysis is incomplete or invalid.
Findings: <list>
Re-read relevant skill instructions and target artifacts.
Fix only what is required.
Overwrite the same output file.
Return: what changed and why."
)
Completion
After all targets complete:
- Provide per-target completion status.
- List analysis files created.
- Report remaining risks, ambiguities, and any blocked targets.
Related Skills
ryan-mahoney/specops-run-spec
testing
VerifiedTrustedCommunity
This skill should be used when the user asks to "run the spec", "implement the spec", or "execute the spec". Implements every step in a SpecOps implementation spec by delegating each step (or logical group of adjacent steps) to a sequential subagent, conventional-committing each one independently, and — when `roborev` is on the path — running `roborev check` on every commit and `roborev fix` (with spec context, so the fix cannot silently drift the implementation away from the spec) on any commit that fails.
SKILL.mdUpdated Apr 29, 2026
ryan-mahoney/ux-auditor
development
VerifiedTrustedCommunity
Exhaustively audit a top-level UI implementation component against an HTML prototype and produce a grouped markdown checklist of corrections. Use when a user asks for UI parity review, visual QA, design implementation audit, pixel-level drift detection, or behavior/style mismatch analysis between prototype HTML and shipped component code.
SKILL.mdUpdated Apr 28, 2026
ryan-mahoney/specops-spec-conformance
development
VerifiedTrustedCommunity
Audit a SpecOps implementation spec against its source analysis spec to find requirements, policies, contracts, edge cases, error modes, invariants, defaults, side effects, or implementation steps that the implementation has dropped, weakened, contradicted, or silently changed — then patch the implementation spec to restore them. Use this skill whenever the user mentions auditing, comparing, conforming, reconciling, or checking an implementation spec against an analysis spec, finding gaps between two specs, ensuring an implementation spec preserves analysis behavior, or verifying spec derivation or traceability. Also trigger when the user describes "did the implementation spec lose anything from the analysis," "does the implementation match the analysis," "verify the implementation spec covers everything," or asks to confirm one spec is faithful to another. Run this before generating code from an implementation spec and after either spec is edited.
SKILL.mdUpdated Apr 28, 2026
ryan-mahoney/specops-spec-coherence
development
VerifiedTrustedCommunity
Audit a set of SpecOps analysis specs for cross-spec coherence — establish a dependency-ordered implementation sequence, then verify pairwise integration contracts at module boundaries plus three cross-cutting consistency dimensions (shared data models, side-effect ownership, terminology) — and patch the affected specs to resolve gaps. Use this skill whenever the user mentions cross-spec consistency, integration gaps between specs, conflicts between specs, duplicate work across specs, implementation order, dependency order for migration, building an implementation-order checklist, ensuring specs interoperate, terminology drift across specs, or shared data model conflicts. Also trigger when the user describes "do my specs agree with each other," "what order should I implement these in," "find inconsistencies across all my specs," or asks to audit a folder of analysis specs as a set rather than individually. Run this once after generating a full set of analysis specs, before deriving implementation specs.
SKILL.mdUpdated Apr 28, 2026