generate-project-plan

Generate a FigJam project plan board from a PRD plus codebase context. Interactive flow: research → propose sections → per-section deep research → per-section content + block-shape proposal → create FigJam → skeleton → fill → diagrams → wrap. Each content block (section, nested section, intro callout, table, multi-column text, sticky column, diagram section, metadata strip) has its own subskill reference file. Use when the user asks for 'project plan in FigJam', 'interactive project plan', '/generate-project-plan', or provides a PRD and wants per-section confirmation on content + rendering.

Quality

92%

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

Quality

Content

85%

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

The body is highly actionable with executable code, clear validation-gated workflows, and well-organized one-level-deep references. Its main weakness is conciseness: inline color/typography tables and a corrective table repeat guidance already present in the referenced foundation files and earlier sections.

Suggestions

Move the full color/typography/section-properties tables into foundation/palette.md and foundation/layout.md, keeping only the single most-load-bearing constant per topic inline so the body earns its conciseness score.

Fold the 'What NOT to use' table into the relevant earlier sections (Colors, Tables) or into plugin-api-traps.md to eliminate the duplication of palette and table-header guidance.

In the Operational rules section, drop the restated STRICT palette/section-name paragraphs that already appear verbatim in the Visual UI conventions block, linking instead to the source-of-truth file.

Dimension	Reasoning	Score
Conciseness	The body mostly avoids explaining concepts Claude already knows and is operationally dense, but it retains sizable inline color/typography tables and a 'What NOT to use' table that duplicate guidance also stated in the Colors/Tables sections and in the referenced foundation files; it could be tightened by pushing more constants into palette.md/layout.md. It is not a score-1 wall of generic padding, but it is not fully lean either.	2 / 3
Actionability	Provides executable JS code blocks (wrapper creation, reparent loop, re-stack pass, first-run probe), exact MCP tool calls with concrete args, specific hex/font/gap constants, and a corrective 'What NOT to use' table — copy-paste ready and complete.	3 / 3
Workflow Clarity	Nine clearly numbered, typed steps each carry inputs, tools/refs, action bullets, and explicit checkpoints; Write steps use screenshot + AskUserQuestion, Research steps have self-checks, and Step 7/Step 9 add re-stack and fix-not-regenerate feedback loops for destructive board operations.	3 / 3
Progressive Disclosure	SKILL.md is an overview with one-level-deep references to verified existing files (foundation/, section-catalog.md, 9 blocks/.md), navigated via a clear block-to-file-to-trigger table and inline links; content is appropriately split, and the inline visual-conventions summary is explicitly justified as a pointer to the source-of-truth files.	3 / 3
	Total	11 / 12 Passed

Description

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.

The description is specific, trigger-rich, and complete, clearly stating both the capability and when to use it with natural phrasing. It is distinct and unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Names a concrete primary action ('Generate a FigJam project plan board from a PRD plus codebase context') plus a full interactive flow chain and an enumeration of 8 distinct content block types, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly states what it does (generate a FigJam project plan board from a PRD) and provides an explicit 'Use when...' clause with multiple triggers, satisfying both the what and the when.	3 / 3
Trigger Term Quality	Includes natural phrases a user would actually say ('project plan in FigJam', 'interactive project plan', '/generate-project-plan', 'PRD ... per-section confirmation'), giving good coverage rather than jargon.	3 / 3
Distinctiveness Conflict Risk	The niche is specific (FigJam project plan boards built from a PRD with per-section confirmation) with distinct triggers, making overlap with other skills unlikely.	3 / 3
	Total	12 / 12 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
relative_links	Relative link issues: 17 deeper-than-1-level	Warning
referenced_paths_exist	Referenced path issues: 18 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: figma/mcp-server-guide
Path: workflow-skills/generate-project-plan/SKILL.md
Commit: 07316dd

Reviewed: about 16 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.