speckit-taskstoissues

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/speckit-taskstoissues/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

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

The body is a clear, actionable, well-guarded batch workflow with explicit validation checkpoints, but it carries notable redundancy from the duplicated pre/post hook-handling blocks and lacks an error-recovery feedback loop.

Suggestions

De-duplicate the Pre-Execution and Post-Execution hook sections by extracting a single shared hook-handling template and referencing it for both before/after phases.

Add an explicit feedback loop for the batch issue-creation step (e.g. verify each issue was created, retry or report on failures) to strengthen workflow_clarity.

Specify which task fields map to which GitHub issue fields (title, body, dependencies/labels) so the MCP issue-creation step is fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly directive and avoids explaining concepts Claude already knows, but the Pre-Execution and Post-Execution hook sections are near-duplicates (~40 lines repeated) that could be tightened into a shared template, leaving some unnecessary length.	3 / 5
Actionability	It provides concrete, executable commands ('check-prerequisites.sh --json --require-tasks --include-tasks', 'git config --get remote.origin.url') and exact hook-output templates, with only minor gaps in how issue fields are populated via the GitHub MCP server.	4 / 5
Workflow Clarity	The sequence is clear (Pre-Execution Checks -> Outline -> Post-Execution Checks) with explicit validation checkpoints for the batch issue-creation operation (CAUTION blocks enforcing remote-URL matching), though it lacks a full validate/fix/retry feedback loop.	4 / 5
Progressive Disclosure	The content is well-organized into clearly signaled sections and is self-contained with no nested external references, but no bundle files are present and the duplicated hook templates could arguably be factored out, leaving minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

53%Weight 40%Scale 1-5

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 is third-person and conveys a clear, specific purpose, but it omits any explicit 'when to use' trigger guidance and offers only a single concrete action with limited keyword variety.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g. 'Use when converting a spec-kit feature's tasks into GitHub issues, or when the user asks to create issues from a task list').

Broaden trigger terms with synonyms and artifact names users actually say (e.g. 'tasks', 'task list', 'issues', 'spec-kit', '.specify/') to improve discovery.

Optionally enumerate the concrete actions (e.g. parse tasks, resolve dependencies, create issues) to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain (tasks -> GitHub issues) and concrete actions ('Convert existing tasks into actionable, dependency-ordered GitHub issues ... based on available design artifacts'), but coverage is limited to a single transformation rather than multiple specific actions.	3 / 5
Completeness	It clearly states what the skill does, but provides no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	It includes relevant natural terms ('tasks', 'GitHub issues', 'dependency-ordered') a user might say, but lacks common synonyms or file/artifact extensions and misses natural phrasings like 'create issues from tasks'.	3 / 5
Distinctiveness Conflict Risk	The niche (spec-kit tasks-to-issues conversion) is fairly distinct with specific triggers tied to design artifacts, with only minor overlap risk against adjacent spec-kit issue/plan skills.	4 / 5
	Total	13 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: g14wx/staffSync
Path: .claude/skills/speckit-taskstoissues/SKILL.md
Commit: 682bfbc

Reviewed: 1 day 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.