update-implementation-plan

Updates implementation plan files with structured phases, tasks, and validation criteria.

1|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill update-implementation-plan-ultraviollettnympho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-implementation-plan
Source: https://github.com/ultraviollettnympho/transit-ticket/tree/main/.github/skills/update-implementation-plan
Command: npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill update-implementation-plan-ultraviollettnympho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping implementation plans current when requirements change is error-prone and inconsistent, especially when plans must be executable by AI agents or humans without ambiguity. ## Core Features & Use Cases - Structured Plan Updates: Rewrites an existing implementation plan file using a mandatory Markdown template with front matter, phases, and task tables. - Machine-Readable Output: Enforces deterministic language, standardized identifier prefixes (REQ-, TASK-, GOAL-), and validation rules so plans can be parsed and executed automatically. - Use Case: When a project adds a new feature or upgrades a package, provide the existing plan file and the new requirements, and receive a fully revised plan with phases, dependencies, risks, and testing sections. ## Quick Start Ask the AI to update the implementation plan file with your new requirements for the feature, refactor, or upgrade you are planning.

Frequently Asked Questions about update-implementation-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update an implementation plan with new requirements?

Provide the existing plan file path and describe the new or updated requirements. The skill rewrites the plan using the mandatory template with phases, task tables, dependencies, and validation criteria.

What structure does an AI-executable implementation plan need?

The plan needs YAML front matter with goal, status, and dates, followed by sections for requirements, phased implementation steps with task tables, alternatives, dependencies, files, testing, and risks. All identifiers use prefixes like REQ-, TASK-, and GOAL-.

Where are implementation plan files saved?

Plans are saved in the /plan/ directory using the naming convention [purpose]-[component]-[version].md, where purpose prefixes include upgrade, refactor, feature, data, infrastructure, process, architecture, or design.

What status values can an implementation plan have?

Plans support five status values: Completed, In progress, Planned, Deprecated, and On Hold. The status appears in the front matter and as a badge in the introduction section.

When should I not use this plan template?

Avoid it for informal notes or exploratory brainstorming where rigid structure adds overhead. The template is designed for deterministic, machine-parseable plans intended for autonomous execution, not loose documentation.