notion-spec-to-implementation

Turns product or tech specs into concrete Notion tasks that Claude code can implement. Breaks down spec pages into detailed implementation plans with clear tasks, acceptance criteria, and progress tracking to guide development from requirements to completion.

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./notion-spec-to-implementation/SKILL.md

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill lays out a clear sequenced workflow with specific Notion tool calls, but it is held back by redundancy, deferred (and missing) reference files, and a lack of validation checkpoints around batch task creation. Most dimensions land at the mid anchor: organized and concrete in places, but incomplete and not fully executable as written.

Suggestions

Create the missing reference and example files the body links to (reference/spec-parsing.md, standard-implementation-plan.md, quick-implementation-plan.md, task-creation.md, progress-tracking.md, and examples/*.md), or inline the essential content and remove the dangling links.

Add explicit validation/verification checkpoints to the workflow — e.g., fetch and confirm the task-database schema before creating tasks, and verify each created task's page ID before marking it 'In Progress'.

Collapse the duplicated Quick Start and Implementation Workflow sections into one, and remove the repeated 'Spec Analysis Patterns' restatement, to tighten the body and remove redundancy.

Dimension	Reasoning	Score
Conciseness	The body is mostly procedural and avoids explaining concepts Claude already knows, but it is padded with redundancy — the 7-step Quick Start duplicates the 8-step Implementation Workflow, 'Spec Analysis Patterns' restates Step 2 parsing, and the same 'See reference/…' pointers recur — so it 'could be tightened' rather than earning the lean-and-efficient top anchor.	2 / 3
Actionability	It names specific Notion tools and gives a few concrete property examples (e.g., 'Status: To Do', 'parent: { data_source_id: "collection://…" }'), but the real detail for spec parsing, plan templates, task-creation patterns, and progress tracking is deferred to reference files that do not exist, and the fenced blocks hold prose rather than executable code — matching 'some concrete guidance but incomplete; missing key details'.	2 / 3
Workflow Clarity	Steps 1–8 are clearly sequenced, but the workflow performs batch task creation and page mutation with no validation or verification checkpoints (no schema confirmation before creating tasks, no success check after creation); per the scoring notes, missing validation in batch operations caps workflow clarity at 2.	2 / 3
Progressive Disclosure	The body is sectioned with clearly signaled one-level-deep references (e.g., 'See [reference/spec-parsing.md]'), but every referenced file — reference/spec-parsing.md, standard-implementation-plan.md, quick-implementation-plan.md, task-creation.md, progress-tracking.md, and the examples/* files — is missing, so the disclosure design is sound yet the navigation is broken and detail is deferred to nothing.	2 / 3
	Total	8 / 12 Passed

Description

67%

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 states concrete capabilities and occupies a clear, distinctive niche, but it lacks an explicit 'Use when…' trigger clause and only offers a limited range of natural trigger-term variations. Adding explicit when-to-use guidance and broader trigger phrasing would raise its completeness and trigger-term quality.

Suggestions

Append an explicit 'Use when…' clause naming the situations that should trigger this skill (e.g., 'Use when turning a Notion spec or PRD into implementation tasks, breaking requirements into a tracked task list, or planning implementation from a spec page').

Broaden trigger-term coverage to include common variations users actually say, such as 'PRD', 'requirements', 'feature spec', 'Notion database', and 'break down a spec'.

Trim the trailing generic phrase 'to guide development from requirements to completion' — it adds fluff without a concrete action.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Turns product or tech specs into concrete Notion tasks', 'Breaks down spec pages into detailed implementation plans with clear tasks, acceptance criteria, and progress tracking' — matching the 'lists multiple specific concrete actions' anchor, not the level below which only names a domain plus a few actions.	3 / 3
Completeness	It clearly answers 'what' the skill does, but there is no 'Use when…' clause or equivalent explicit trigger guidance, so 'when' is only implied — per the judging guidelines a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	'specs', 'Notion tasks', and 'implementation plans' are relevant natural terms, but coverage of variations is limited (no 'PRD', 'requirements', 'Notion database', or 'feature spec'), so it sits at 'some relevant keywords but missing common variations' rather than the full-coverage anchor above.	2 / 3
Distinctiveness Conflict Risk	It targets a clear niche (Notion spec→implementation task creation) with distinct triggers, making it unlikely to fire for the wrong skill, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 13 missing	Warning

	Total	15 / 16 Passed

Repository: Prat011/awesome-llm-skills
Path: notion-spec-to-implementation/SKILL.md
Commit: 35e1ea2

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

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.