Skip to content
Back to skills

Spec Synthesizer

ASecurity

Synthesizes multiple review reports and analyses into a single prioritized, actionable implementation plan.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 4, 2026
ai-agents

Security analysis

A100/100

Scanned October 4, 2026

npx -y skills add nseney1/Soma-Governance --skill spec-synthesizer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Spec Synthesizer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Spec Synthesizer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nseney1-spec-synthesizer/badge)](https://www.skillsdirectory.com/skills/nseney1-spec-synthesizer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: Spec Synthesizer
description: Synthesizes multiple review reports and analyses into a single prioritized, actionable implementation plan.
trigger: user_request
---

# Spec Synthesizer

> **Role**: Ingests N input artifacts (post-mortems, reviews, audits, architectural assessments) and synthesizes them into a single deduplicated, prioritized implementation plan.

## Workflow

1. **Read Artifacts**: Read all input artifacts provided by the orchestrator.
2. **Extract Findings**: Extract all concrete issues, recommendations, and architectural findings into a unified list.
3. **Deduplicate & Score Confidence**:
   - Findings corroborated across 2+ sources receive **HIGH** confidence.
   - Findings originating from a single source receive **MEDIUM** confidence.
4. **Group by Component**: Organize findings logically by component, service, or feature area.
5. **Prioritize (Impact × Effort)**: Rank fixes primarily by impact, ordering high-impact / low-effort tasks first.
6. **Generate Implementation Plan**: Produce an actionable `implementation_plan.md` adhering to the required structure.

## Input Format (From Orchestrator)

```text
Synthesize these artifacts into an implementation plan:
1. [path] — description
2. [path] — description
Project context: [brief]
Constraints: [budget, timeline, breaking changes]
```

## Output Format

```markdown
# Consolidated Implementation Plan

## Tier 1: High Impact, Low Effort
### [Component Name]
- **Finding**: [description] (Sources: [artifact1], [artifact2]) [HIGH confidence]
- **Proposed fix**: [specific change]
- **Files**: [list of affected files]
- **Verification**: [concrete test commands or validation criteria]

## Tier 2: High Impact, Medium Effort
### [Component Name]
- **Finding**: [description] (Sources: [artifact1]) [MEDIUM confidence]
- **Proposed fix**: [specific change]
- **Files**: [list of affected files]
- **Verification**: [concrete test commands or validation criteria]

## Tier 3: Medium/Low Impact or High Effort
...

## Open Questions & Trade-offs
- [question requiring user input or architectural decision]
```

## Anti-Patterns & Failure Modes

- **Hallucinated Findings**: Do not add findings that are not explicitly present in the source artifacts.
- **Dropping Single-Source Findings**: Do not silently drop single-source findings; retain them with explicit `[MEDIUM confidence]` tagging.
- **Ease-First Inversion**: Do not reorder tasks by ease alone—impact must remain the primary prioritization axis.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.