project-workflow
Nine integrated slash commands for complete project lifecycle: /explore-idea, /plan-project, /plan-feature, /wrap-session, /continue-session, /workflow, /release, /brief, /reflect. Use when starting projects, managing sessions across context windows, capturing learnings, or preparing releases. Saves 35-55 minutes per lifecycle.
Install with Tessl CLI
npx tessl i github:jezweb/claude-skills --skill project-workflow80
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
77%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 description effectively lists specific commands and provides clear 'Use when' guidance, making it functionally complete. However, the trigger terms lean toward technical slash command names rather than natural user language, and the broad 'project lifecycle' scope could potentially conflict with other planning-focused skills. The time-saving claim (35-55 minutes) is marketing fluff that doesn't aid skill selection.
Suggestions
Add more natural trigger terms users would actually say, such as 'new project', 'save my progress', 'pick up where I left off', 'document what I learned'
Clarify the distinct niche by specifying what type of projects or workflows this targets (e.g., software development, creative projects) to reduce conflict risk with other planning skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists nine specific slash commands by name (/explore-idea, /plan-project, etc.) and describes concrete lifecycle phases (starting projects, managing sessions, capturing learnings, preparing releases). | 3 / 3 |
Completeness | Clearly answers both what (nine integrated slash commands for project lifecycle) and when (starting projects, managing sessions, capturing learnings, preparing releases) with explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes some natural terms like 'starting projects', 'releases', 'sessions', but the slash command names are technical and users might not naturally say 'explore-idea' or 'wrap-session'. Missing common variations like 'new project', 'save progress', 'document learnings'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'project lifecycle' and 'session management' concepts are somewhat specific, but terms like 'plan-project' and 'plan-feature' could overlap with other planning or project management skills. The slash command format helps distinguish it. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill document that efficiently describes 9 integrated commands with clear workflows and relationships. The main weakness is the lack of concrete, executable examples showing actual command invocation and expected outputs. The document would benefit from splitting detailed reference content into separate files.
Suggestions
Add concrete usage examples showing actual command invocation syntax and sample outputs (e.g., what `/explore-idea my-app-concept` produces)
Move the detailed Command Relationships diagram and Time Savings table to a separate REFERENCE.md file, keeping only the essential workflow examples in the main skill
Add links to the referenced skills (project-planning, project-session-management) in the Integration section
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables, bullet points, and structured sections without explaining concepts Claude already knows. Every section serves a purpose with no padding or unnecessary explanations. | 3 / 3 |
Actionability | Commands are well-described with clear 'Use when' and 'Does' sections, but lacks executable code examples. The installation section mentions copying files but doesn't show the actual command structure or provide concrete usage examples beyond descriptions. | 2 / 3 |
Workflow Clarity | Excellent workflow visualization with the ASCII diagram showing command relationships, clear workflow examples (Full vs Quick), and explicit prerequisites. The command sequence is unambiguous with clear handoff points between phases. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is monolithic at ~200 lines. The Integration section references other skills but doesn't link to them. Some content (like the full Command Relationships diagram) could be in a separate reference file. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 12 / 16 Passed | |
- 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.