pm-planner

PM Planner Agent. 기능 기획, 요구사항 정의, 명세서 작성을 담당합니다. 기획, 명세, 요구사항, PRD, 스펙 관련 요청 시 사용됩니다.

Quality

59%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/pm-planner/SKILL.md

Quality

Content

37%

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

This skill provides useful templates and output locations but functions more as a role description than actionable guidance. It lacks workflow clarity for actually executing PM tasks and includes methodology explanations that Claude already knows. The PRD template is the strongest element, being concrete and copy-paste ready.

Suggestions

Add a clear numbered workflow for creating a PRD (e.g., 1. Gather requirements via X, 2. Draft user stories, 3. Review with stakeholder, 4. Finalize)

Remove or move MoSCoW and RICE explanations to a separate reference file - Claude knows these frameworks

Add validation checkpoints (e.g., 'Before finalizing PRD, verify: all user stories have acceptance criteria, all Must-haves are technically feasible')

Include a concrete example of a completed user story or requirement to demonstrate expected quality

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some explanatory content Claude already knows (MoSCoW methodology, RICE scoring definitions). The template structure is useful but the methodology explanations could be trimmed.	2 / 3
Actionability	Provides concrete templates and file paths which are helpful, but lacks executable guidance on HOW to actually perform the tasks. The PRD template is copy-paste ready, but there's no guidance on the actual process of gathering requirements or writing effective user stories.	2 / 3
Workflow Clarity	No clear workflow or sequence for creating documents. Lists responsibilities but doesn't explain the order of operations, validation steps, or how to iterate on feedback. Missing any process for reviewing or validating the produced documents.	1 / 3
Progressive Disclosure	Content is organized into logical sections with clear headers. However, the methodology explanations (MoSCoW, RICE) could be moved to separate reference files. Output locations are specified but no links to related skills or detailed guides.	2 / 3
	Total	7 / 12 Passed

Description

82%

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 reasonably well-structured skill description that clearly communicates both purpose and trigger conditions in Korean. It has strong trigger term coverage with natural PM terminology and explicit 'when to use' guidance. The main weakness is that the capability descriptions are somewhat categorical rather than listing specific concrete actions.

Suggestions

Add more specific concrete actions like 'user story 작성, 기능 흐름도 설계, API 명세 정의' to improve specificity

Consider adding file type triggers if applicable (e.g., '.md', 'Notion', 'Confluence') to further distinguish from other documentation skills

Dimension	Reasoning	Score
Specificity	Names the domain (PM/planning) and lists some actions ('기능 기획, 요구사항 정의, 명세서 작성' - feature planning, requirements definition, specification writing), but these are somewhat general categories rather than highly specific concrete actions.	2 / 3
Completeness	Clearly answers both what ('기능 기획, 요구사항 정의, 명세서 작성을 담당합니다') and when ('기획, 명세, 요구사항, PRD, 스펙 관련 요청 시 사용됩니다') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes good coverage of natural Korean terms users would say: '기획' (planning), '명세' (specification), '요구사항' (requirements), 'PRD', '스펙' (spec). These are terms product managers and developers naturally use.	3 / 3
Distinctiveness Conflict Risk	Reasonably specific to PM/planning domain, but could potentially overlap with general documentation skills or technical writing skills. The PRD and spec focus helps distinguish it somewhat.	2 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Repository: shaul1991/shaul-agents-plugin
Commit: 9242c58

Reviewed: 4 months 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.