sdd-archive
Sync delta specs to main specs and archive a completed change. Trigger: When the orchestrator launches you to archive a change after implementation and verification.
78
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/sdd-archive/SKILL.mdQuality
Discovery
59%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description has a clear trigger clause and a distinct niche, which are strengths. However, it relies heavily on internal jargon ('delta specs', 'main specs', 'orchestrator') without explaining what these terms mean, and the specific actions involved in syncing and archiving are underspecified. The trigger terms are not natural user language, which significantly limits discoverability.
Suggestions
Replace or supplement jargon like 'delta specs' and 'main specs' with more natural terms or brief explanations so the skill can be matched by users unfamiliar with the internal terminology.
Add more concrete action descriptions, e.g., 'Merges incremental change specifications into the canonical spec document, removes the delta file, and updates the change log.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names a domain ('delta specs', 'main specs', 'archive a completed change') and describes some actions ('sync' and 'archive'), but doesn't list multiple concrete actions or explain what syncing/archiving entails in detail. | 2 / 3 |
Completeness | It explicitly answers both 'what does this do' (sync delta specs to main specs and archive a completed change) and 'when should Claude use it' (when the orchestrator launches you to archive a change after implementation and verification), with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | The trigger terms are highly specialized jargon ('delta specs', 'main specs', 'orchestrator') that a user would not naturally say. There are no common natural-language keywords a user would use to invoke this skill. | 1 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to a particular workflow involving delta specs, main specs, and orchestrator-driven archiving, making it very unlikely to conflict with other skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with clear multi-step workflows, explicit validation checkpoints, and concrete file paths and commands. It handles four distinct artifact store modes systematically, though the repeated mode-branching across steps adds some verbosity. The safety rules and merge instructions are specific and actionable, making this a strong operational skill.
Suggestions
Consider consolidating the mode-based branching into a decision table at the top of the 'What to Do' section, then referencing it in each step, to reduce repetition and improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but has some redundancy — the mode-based branching (engram/openspec/hybrid/none) is repeated across nearly every step, which could be consolidated into a single decision matrix. Some sections like the return summary template are appropriately detailed but the overall document could be tighter. | 2 / 3 |
Actionability | The skill provides concrete, executable guidance: specific file paths, bash commands for copying, pseudocode for merge logic with clear matching criteria, a checklist for verification, and a complete markdown template for the return summary. The merge instructions specify exactly how to handle added/modified/removed requirements. | 3 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced with explicit validation in Step 4 (checklists per mode), a mandatory persistence step (Step 5), and a safety rule against archiving changes with CRITICAL issues. The destructive operation warning rule and the 'sync before archive' ordering provide appropriate feedback loops and safeguards. | 3 / 3 |
Progressive Disclosure | The skill appropriately references shared conventions (`sdd-phase-common.md` Sections A-D, `openspec-convention.md`) without inlining their content, keeping references one level deep and clearly signaled. The main content stays focused on archive-specific logic while delegating common patterns to shared files. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Gentleman-Programming/agent-teams-lite
- Commit
6901875
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.