spec-generator
Specification generator - 7 phase document chain producing product brief, PRD, architecture, epics, and issues. Agent-delegated heavy phases (2-5, 6.5) with Codex review gates. Triggers on "generate spec", "create specification", "spec generator", "workflow:spec".
68
85%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that concisely communicates what the skill does (multi-phase specification document generation), what it produces (product brief, PRD, architecture, epics, issues), and when to use it (explicit trigger terms). It uses third person voice appropriately and avoids vague language or buzzwords. The only minor weakness is that some terms like 'Codex review gates' and 'Agent-delegated heavy phases (2-5, 6.5)' are implementation details that may not help with skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and outputs: '7 phase document chain producing product brief, PRD, architecture, epics, and issues.' Also mentions agent-delegated phases and Codex review gates, which are concrete implementation details. | 3 / 3 |
Completeness | Clearly answers both 'what' (7 phase document chain producing product brief, PRD, architecture, epics, and issues with agent-delegated phases and review gates) and 'when' (triggers on 'generate spec', 'create specification', 'spec generator', 'workflow:spec'). | 3 / 3 |
Trigger Term Quality | Includes explicit trigger terms that users would naturally say: 'generate spec', 'create specification', 'spec generator', 'workflow:spec'. These cover common variations of how a user would request this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: specification generation through a specific 7-phase workflow. The explicit trigger terms and detailed output types (product brief, PRD, architecture, epics, issues) make it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable and well-structured orchestration skill with excellent workflow clarity, explicit validation gates, and clean progressive disclosure to phase-specific documents. However, it suffers significantly from verbosity — the same information (agent parameters, fork strategy rationale, timeout values) is repeated across multiple sections (Architecture Overview, Agent Registry, Fork Context Strategy, Lifecycle Management, Execution Flow), roughly tripling the token cost without adding new information. The skill would benefit enormously from consolidation.
Suggestions
Consolidate the Agent Registry, Fork Context Strategy, and Lifecycle Management sections into a single compact table — currently fork_turns:'none' and 30min timeout are stated 5+ times across different sections.
Remove the Fork Context Strategy section entirely — the rationale ('pipeline pattern, context passed via files') is stated once in Key Design Principles and doesn't need a dedicated 15-row table repeating 'none' for every agent.
Merge the Timeout Protocol table into the Error Handling table since timeout actions are already listed there, eliminating another redundant section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~400+ lines with massive repetition. The agent registry, fork context strategy, lifecycle management, and timeout protocol tables all repeat the same information (fork_turns: 'none', 30min timeout, same pattern) multiple times. The context envelope template, post-agent validation code, and cleanup protocol could be dramatically condensed. Much of this content explains orchestration patterns Claude can infer from a compact specification. | 1 / 3 |
Actionability | The skill provides highly concrete, executable guidance: specific spawn_agent/wait_agent/close_agent calls with exact parameters, JSON schemas for spec-config.json, directory structures with exact naming conventions, timeout values, error handling tables with specific actions, and code snippets for session ID generation, validation, and cleanup. Everything is copy-paste ready. | 3 / 3 |
Workflow Clarity | The 7-phase pipeline is exceptionally well-sequenced with explicit phase transitions (update_plan calls), validation checkpoints after each agent phase (file existence checks, spec-config.json verification), error recovery paths (timeout cascade: status probe → force finalize → close → inline fallback), and iteration limits (Phase 6.5 max 2 iterations). The readiness check scoring thresholds (>=80% pass, 60-79% review, <60% fail) provide clear decision gates. | 3 / 3 |
Progressive Disclosure | The skill is structured as an orchestrator overview with clear one-level-deep references to phase documents (phases/01-discovery.md through phases/07-issue-export.md), templates, specs, and profiles. The 'Reference Documents by Phase' section provides well-organized navigation tables. Content is appropriately split between the SKILL.md overview and phase-specific detail files, though no bundle files were provided to verify their existence. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (564 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- catlog22/Claude-Code-Workflow
- Commit
5ff5e86
- 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.