plan

Draft repo plans and generate matching issues contracts from templates.

130|17|Updated Dec 20, 2025

Search Tags:#automation #planning #templates #repository #csv #plan

Ready to run

npx skills add https://github.com/appautomaton/agent-designer --skill plan-appautomaton

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/appautomaton/agent-designer/tree/main/.codex/skills/plan
Command: npx skills add https://github.com/appautomaton/agent-designer --skill plan-appautomaton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

Draft structured repo plans and automatically generate the associated issues contracts, reducing planning friction for teams working on Codex-style SKILLs and MCP-driven workflows.

Core Features & Use Cases

Use the built-in plan template (assets/_template.md) to standardize planning output.
Save finalized plans to the repo plan/ directory and generate a matching Issues CSV path under issues/.
Validate naming, timestamps, and frontmatter to ensure consistency across planning workflows and tool integrations.

Quick Start

Draft a plan for this repository using the plan template and save it to plan/ with a matching issues CSV.

Frequently Asked Questions about plan

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

FAQPage Schema

How do I generate a repository plan and matching issues contract from a template?▼

Validate plan files by running the provided validation scripts to check naming conventions, timestamps, and frontmatter consistency before finalizing your repository plan and issues contract.

What is the best way to standardize planning output for Codex-style SKILLs and MCP-driven workflows?▼

Draft structured repository plans and automatically generate the associated issues contracts to reduce planning friction for teams working on Codex-style SKILLs and MCP-driven workflows.

Can I use this planning workflow to validate frontmatter and naming conventions in CSV files?▼

The validation scripts check your generated issues CSV files and plan documents to ensure they adhere to the required frontmatter and timestamped naming conventions.

Do I need to reference MCP tool documentation when drafting repo plans?▼

Referencing the MCP tools documentation ensures that your generated plan files and issues contracts correctly integrate with the supported MCP-driven workflows.

Why does my issues CSV file need a timestamped filename?▼

Timestamped filenames on issues CSV files prevent naming collisions and maintain chronological consistency when generating multiple repository plans over time.

When do I need a structured repository plan and issues contract?▼

Generating a matching issues contract alongside your repository plan is necessary when you want to validate frontmatter and ensure consistency across tool integrations.