update-implementation-plan
Update an existing implementation plan file with new or update requirements to provide new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.
Install with Tessl CLI
npx tessl i github:github/awesome-copilot --skill update-implementation-plan59
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
32%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 provides a reasonable overview of what the skill does but lacks explicit trigger guidance ('Use when...'), which is critical for skill selection. The actions described are somewhat generic ('update', 'provide new features') and the trigger terms could overlap with other development-related skills.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'update plan', 'modify implementation', 'change requirements', 'revise spec'
List more specific concrete actions such as 'add new requirements sections', 'mark completed tasks', 'update architecture diagrams', 'revise package versions'
Include file-related triggers like '.md plan files', 'PLAN.md', or 'implementation document' to distinguish from general coding skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (implementation plan files) and some actions (update with new requirements, refactoring, upgrading packages), but the actions are somewhat generic and not comprehensively specific about what 'updating' entails. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this is weaker than that threshold. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'implementation plan', 'refactoring', 'upgrading packages', 'architecture', but missing common variations users might say like 'update plan', 'modify spec', 'change requirements', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | Focuses on 'implementation plan file' which provides some specificity, but terms like 'design', 'architecture', 'refactoring' are broad and could overlap with general coding or architecture skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive and actionable template for implementation plans with good structure and concrete examples. However, it lacks an explicit workflow for the UPDATE process itself (reading existing plans, merging changes, validation), and contains unnecessary framing about AI-to-AI communication that adds tokens without value.
Suggestions
Add an explicit step-by-step workflow for updating existing plans: 1) Read current plan, 2) Identify sections needing updates, 3) Merge new requirements, 4) Validate template compliance, 5) Update status/dates
Remove or significantly condense the 'AI-to-AI communication' and 'machine-readable' framing - Claude understands these concepts implicitly
Add validation checkpoints, e.g., 'Before saving: verify all REQ- identifiers are unique, all TASK- items have descriptions, front matter status matches completion state'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity like 'AI-to-AI communication' framing and repeated emphasis on 'machine-readable' concepts that Claude already understands. The template itself is useful but the preamble could be significantly tightened. | 2 / 3 |
Actionability | Provides a complete, copy-paste ready markdown template with specific naming conventions, directory paths, required sections, and concrete examples of identifiers (REQ-001, TASK-001, etc.). The template is fully executable. | 3 / 3 |
Workflow Clarity | While the template structure is clear, there's no explicit workflow for HOW to update an existing plan - no steps for reading the current plan, identifying what needs updating, validating changes, or handling conflicts between old and new requirements. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the skill is somewhat monolithic - the full template could be referenced from a separate file. No external references are provided for complex topics like validation rules or status definitions. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.