create-implementation-plan

Name: create-implementation-plan
Author: github

12kinstalls4.6kforks

How to install create-implementation-plan?

github/awesome-copilot/create-implementation-plan

$npx -y skills add github/awesome-copilot --skill create-implementation-plan

Installs into the current project.

Summary

Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.

Files · 1

View on GitHub

SKILL.md

1	# Create Implementation Plan
2
3	## Primary Directive
4
5	Your goal is to create a new implementation plan file for `${input:PlanPurpose}`. Your output must be machine-readable, deterministic, and structured for autonomous execution by other AI systems or humans.
6
7	## Execution Context
8
9	This prompt is designed for AI-to-AI communication and automated processing. All instructions must be interpreted literally and executed systematically without human interpretation or clarification.
10
11	## Core Requirements
12
13	- Generate implementation plans that are fully executable by AI agents or humans
14	- Use deterministic language with zero ambiguity
15	- Structure all content for automated parsing and execution
16	- Ensure complete self-containment with no external dependencies for understanding
17
18	## Plan Structure Requirements
19
20	Plans must consist of discrete, atomic phases containing executable tasks. Each phase must be independently processable by AI agents or humans without cross-phase dependencies unless explicitly declared.
21
22	## Phase Architecture
23
24	- Each phase must have measurable completion criteria
25	- Tasks within phases must be executable in parallel unless dependencies are specified
26	- All task descriptions must include specific file paths, function names, and exact implementation details
27	- No task should require human interpretation or decision-making
28
29	## AI-Optimized Implementation Standards
30
31	- Use explicit, unambiguous language with zero interpretation required
32	- Structure all content as machine-parseable formats (tables, lists, structured data)
33	- Include specific file paths, line numbers, and exact code references where applicable
34	- Define all variables, constants, and configuration values explicitly
35	- Provide complete context within each task description
36	- Use standardized prefixes for all identifiers (REQ-, TASK-, etc.)
37	- Include validation criteria that can be automatically verified
38
39	## Output File Specifications
40
41	- Save implementation plan files in `/plan/` directory
42	- Use naming convention: `[purpose]-[component]-[version].md`
43	- Purpose prefixes: `upgrade\|refactor\|feature\|data\|infrastructure\|process\|architecture\|design`
44	- Example: `upgrade-system-command-4.md`, `feature-auth-module-1.md`
45	- File must be valid Markdown with proper front matter structure
46
47	## Mandatory Template Structure
48
49	All implementation plans must strictly adhere to the following template. Each section is required and must be populated with specific, actionable content. AI agents must validate template compliance before execution.
50
51	## Template Validation Rules
52
53	- All front matter fields must be present and properly formatted
54	- All section headers must match exactly (case-sensitive)
55	- All identifier prefixes must follow the specified format
56	- Tables must include all required columns
57	- No placeholder text may remain in the final output
58	- Identifiers must be uniquely declared. Every identifier (`REQ-NNN`, `SEC-NNN`, `CON-NNN`, `GUD-NNN`, `PAT-NNN`, `GOAL-NNN`, `TASK-NNN`, `ALT-NNN`, `DEP-NNN`, `FILE-NNN`, `TEST-NNN`, `RISK-NNN`, `ASSUMPTION-NNN`) must be declared exactly once. A declaration is where the identifier introduces a row: the leading cell in a TASK/GOAL table row, or the bolded prefix in a bullet line like `- REQ-001: ...`. The same identifier may then appear any number of times as a reference elsewhere in the plan (a `TASK` body citing a `REQ`, one `TASK` citing another `TASK`, the Dependencies section pointing at a `DEP` already declared upstream, etc.). References are expected and not collisions.
59
60	## Identifier Uniqueness Check
61
62	Run these checks before finalizing the plan. Checks (1) and (2) target declarations and must return zero rows. Check (3) is a broad informational scan: it will surface valid references too, so use it for awareness rather than as a gate.
63
64	```bash
65	# Set PLAN_FILE to the plan being validated.
66	PLAN_FILE="/plan/<purpose>-<component>-<version>.md"
67
68	# 1) Duplicate TASK / GOAL declarations in table rows.
69	grep -oE '\\| (TASK\|GOAL)-[0-9]+ \\|' "$PLAN_FILE" \
70	\| sed -E 's/.((TASK\|GOAL)-[0-9]+)./\1/' \
71	\| sort \| uniq -d
72
73	# 2) Duplicate declaration IDs in bullet-style spec lines.
74	grep -oE '^- \\(REQ\|SEC\|CON\|GUD\|RISK\|ASSUMPTION\|TASK\|GOAL\|FILE\|TEST\|PAT\|ALT\|DEP)-[0-9]+\\:' "$PLAN_FILE" \
75	\| sed -E 's/^- \\([A-Z]+-[0-9]+)\\:.*/\1/' \
76	\| sort \| uniq -d
77
78	# 3) Broad duplicate scan (diagnostic only; may include valid references).
79	grep -oE '(REQ\|SEC\|CON\|GUD\|RISK\|ASSUMPTION\|TASK\|GOAL\|FILE\|TEST\|PAT\|ALT\|DEP)-[0-9]+' "$PLAN_FILE" \
80	\| sort \| uniq -d
81	```
82
83	Prerequisites: a POSIX-compatible shell (`sh` / `bash`) with `grep`, `sed`, `sort`, and `uniq`. On Windows without these tools, use equivalent platform-native commands and preserve the same declaration-vs-reference logic.
84
85	If check (1) or (2) returns any row, re-number t

People who liked this also viewed

6 picks

Type

create-implementation-plan

12kinstalls4.6kforks

View on GitHub

How to install create-implementation-plan?

github/awesome-copilot/create-implementation-plan

$npx -y skills add github/awesome-copilot --skill create-implementation-plan

Installs into the current project.

Summary

Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.

Files · 1

View on GitHub

SKILL.md

1	# Create Implementation Plan
2
3	## Primary Directive
4
5	Your goal is to create a new implementation plan file for `${input:PlanPurpose}`. Your output must be machine-readable, deterministic, and structured for autonomous execution by other AI systems or humans.
6
7	## Execution Context
8
9	This prompt is designed for AI-to-AI communication and automated processing. All instructions must be interpreted literally and executed systematically without human interpretation or clarification.
10
11	## Core Requirements
12
13	- Generate implementation plans that are fully executable by AI agents or humans
14	- Use deterministic language with zero ambiguity
15	- Structure all content for automated parsing and execution
16	- Ensure complete self-containment with no external dependencies for understanding
17
18	## Plan Structure Requirements
19
20	Plans must consist of discrete, atomic phases containing executable tasks. Each phase must be independently processable by AI agents or humans without cross-phase dependencies unless explicitly declared.
21
22	## Phase Architecture
23
24	- Each phase must have measurable completion criteria
25	- Tasks within phases must be executable in parallel unless dependencies are specified
26	- All task descriptions must include specific file paths, function names, and exact implementation details
27	- No task should require human interpretation or decision-making
28
29	## AI-Optimized Implementation Standards
30
31	- Use explicit, unambiguous language with zero interpretation required
32	- Structure all content as machine-parseable formats (tables, lists, structured data)
33	- Include specific file paths, line numbers, and exact code references where applicable
34	- Define all variables, constants, and configuration values explicitly
35	- Provide complete context within each task description
36	- Use standardized prefixes for all identifiers (REQ-, TASK-, etc.)
37	- Include validation criteria that can be automatically verified
38
39	## Output File Specifications
40
41	- Save implementation plan files in `/plan/` directory
42	- Use naming convention: `[purpose]-[component]-[version].md`
43	- Purpose prefixes: `upgrade\|refactor\|feature\|data\|infrastructure\|process\|architecture\|design`
44	- Example: `upgrade-system-command-4.md`, `feature-auth-module-1.md`
45	- File must be valid Markdown with proper front matter structure
46
47	## Mandatory Template Structure
48
49	All implementation plans must strictly adhere to the following template. Each section is required and must be populated with specific, actionable content. AI agents must validate template compliance before execution.
50
51	## Template Validation Rules
52
53	- All front matter fields must be present and properly formatted
54	- All section headers must match exactly (case-sensitive)
55	- All identifier prefixes must follow the specified format
56	- Tables must include all required columns
57	- No placeholder text may remain in the final output
58	- Identifiers must be uniquely declared. Every identifier (`REQ-NNN`, `SEC-NNN`, `CON-NNN`, `GUD-NNN`, `PAT-NNN`, `GOAL-NNN`, `TASK-NNN`, `ALT-NNN`, `DEP-NNN`, `FILE-NNN`, `TEST-NNN`, `RISK-NNN`, `ASSUMPTION-NNN`) must be declared exactly once. A declaration is where the identifier introduces a row: the leading cell in a TASK/GOAL table row, or the bolded prefix in a bullet line like `- REQ-001: ...`. The same identifier may then appear any number of times as a reference elsewhere in the plan (a `TASK` body citing a `REQ`, one `TASK` citing another `TASK`, the Dependencies section pointing at a `DEP` already declared upstream, etc.). References are expected and not collisions.
59
60	## Identifier Uniqueness Check
61
62	Run these checks before finalizing the plan. Checks (1) and (2) target declarations and must return zero rows. Check (3) is a broad informational scan: it will surface valid references too, so use it for awareness rather than as a gate.
63
64	```bash
65	# Set PLAN_FILE to the plan being validated.
66	PLAN_FILE="/plan/<purpose>-<component>-<version>.md"
67
68	# 1) Duplicate TASK / GOAL declarations in table rows.
69	grep -oE '\\| (TASK\|GOAL)-[0-9]+ \\|' "$PLAN_FILE" \
70	\| sed -E 's/.((TASK\|GOAL)-[0-9]+)./\1/' \
71	\| sort \| uniq -d
72
73	# 2) Duplicate declaration IDs in bullet-style spec lines.
74	grep -oE '^- \\(REQ\|SEC\|CON\|GUD\|RISK\|ASSUMPTION\|TASK\|GOAL\|FILE\|TEST\|PAT\|ALT\|DEP)-[0-9]+\\:' "$PLAN_FILE" \
75	\| sed -E 's/^- \\([A-Z]+-[0-9]+)\\:.*/\1/' \
76	\| sort \| uniq -d
77
78	# 3) Broad duplicate scan (diagnostic only; may include valid references).
79	grep -oE '(REQ\|SEC\|CON\|GUD\|RISK\|ASSUMPTION\|TASK\|GOAL\|FILE\|TEST\|PAT\|ALT\|DEP)-[0-9]+' "$PLAN_FILE" \
80	\| sort \| uniq -d
81	```
82
83	Prerequisites: a POSIX-compatible shell (`sh` / `bash`) with `grep`, `sed`, `sort`, and `uniq`. On Windows without these tools, use equivalent platform-native commands and preserve the same declaration-vs-reference logic.
84
85	If check (1) or (2) returns any row, re-number t

People who liked this also viewed

6 picks

Type