Split large implementation plan documents into digestible, hierarchical structures with descriptive names. Use when refactoring monolithic planning docs, organizing phase documentation, or creating contributor-friendly task breakdowns. Triggers: "split this plan", "organize phases", "break down implementation docs", "create task hierarchy".
Overall
score
100%
Does it follow best practices?
Validation for skill structure
This file contains JSON schemas and YAML templates used by the automation scripts. Load ONLY when debugging validation or customizing automation.
Two JSON schemas validate file structure:
Validates step/activity markdown files:
{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"required": ["title", "description", "checklist", "acceptanceCriteria"],
"properties": {
"title": { "type": "string" },
"description": { "type": "string", "minLength": 10 },
"checklist": {
"type": "array",
"items": { "type": "string" },
"minItems": 1
},
"acceptanceCriteria": {
"type": "array",
"items": { "type": "string" },
"minItems": 1
},
"status": {
"type": "string",
"enum": ["not-started", "in-progress", "complete", "blocked"]
},
"dependencies": {
"type": "array",
"items": { "type": "string" }
}
}
}Validates README files:
{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"required": ["title", "description"],
"properties": {
"title": { "type": "string" },
"description": { "type": "string", "minLength": 20 },
"contents": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": { "type": "string" },
"path": { "type": "string" },
"description": { "type": "string" }
}
}
},
"successCriteria": {
"type": "array",
"items": { "type": "string" }
}
}
}Templates are defined in templates/ directory and used by the automation scripts:
Phase-level README with sections: Phase Header, Activities/Steps table, Success Criteria, Rollback Procedure.
title: "Phase {{number}}: {{name}}"
sections:
- name: "Phase Header"
- name: "{{type|title}}" # "Activities" or "Steps"
- name: "Success Criteria"
- name: "Rollback Procedure"Variables: number, name, description, type, type_singular, items[]
Intermediate directory README for activities/ or steps/ folders.
title: "{{type|title}}"
sections:
- name: "Description"
- name: "Groups"Variables: type
Group directory README (e.g., step-1-extract-and-refactor/README.md).
title: "{{type_singular|title}} {{number}}: {{name}}"
sections:
- name: "Description"
- name: "Files"
- name: "Prerequisites"
- name: "Status"Variables: type_singular, number, name, description, sub_items_count, sub_items[]
Step/activity leaf file template.
title: "{{type_singular|title}} {{number}}: {{name}}"
sections:
- name: "Description"
- name: "Checklist"
- name: "Acceptance Criteria"
- name: "Status"
- name: "Notes"
- name: "Dependencies"
defaults:
status: "Not Started"
dependencies: []Variables: type_singular, number, name, description, checklist[], acceptance_criteria[], status, dependencies[]
| Syntax | Description | Example |
|---|---|---|
{{variable}} | Variable interpolation | {{name}} → "Analysis" |
{{kebab value}} | Convert to kebab-case | {{kebab name}} → "analysis-and-design" |
{{value|title}} | Title case filter | {{type|title}} → "Activities" |
{{#each array}}...{{/each}} | Array iteration | Loop through items |
{{#if condition}}...{{/if}} | Conditional | Show if truthy |
{{#if cond}}...{{else}}...{{/if}} | Conditional with else | Show alternate |
Install with Tessl CLI
npx tessl i pantheon-ai/implementation-plan-splitter@0.1.0