save-plan

Saves conversation plans as timestamped ticket-scoped markdown artifacts with frontmatter.

1|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/williamthorsen/codeassembly --skill save-plan-williamthorsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save-plan
Source: https://github.com/williamthorsen/codeassembly/tree/main/packages/agents/content/skills/save-plan
Command: npx skills add https://github.com/williamthorsen/codeassembly --skill save-plan-williamthorsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans produced during AI-assisted conversations are often lost when the session ends. This Skill persists the most recent plan from conversation context as a durable, ticket-scoped markdown artifact with standardized frontmatter, so planning work survives across sessions and can be linked to tickets. ## Core Features & Use Cases - Plan extraction: Captures the most recent plan discussed or produced in the current conversation, including output from built-in plan mode. - Ticket-scoped storage: Resolves session context (ticket ID, project slug, artifact directory) and writes the plan into the correct ticket directory using a timestamped slug naming convention. - Standardized frontmatter: Generates universal artifact frontmatter plus plan provenance fields via a resolver script, keeping artifacts consistent and searchable. - Use Case: After finishing a planning session for an OAuth2 migration, invoke this Skill to save the plan as 20260226-143000Z_oauth2-migration_plan.md under the ticket's artifact directory, then optionally create a ticket for the work. ## Quick Start Ask the agent to save the plan we just discussed as a ticket artifact using the save-plan skill.

Frequently Asked Questions about save-plan

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

FAQPage Schema
How do I save a plan from an AI conversation as a file?

Invoke the save-plan skill after a planning conversation. It extracts the most recent plan from context, resolves the ticket directory, generates frontmatter, and writes a timestamped markdown artifact such as 20260226-143000Z_oauth2-migration_plan.md.

Where are saved plan artifacts stored?

Plans are stored under the artifact base directory resolved from session context, at projects/{project_slug}/tickets/{ticket_id}/. The skill creates the target directory with mkdir -p before writing the file.

What frontmatter does a saved plan artifact include?

The artifact uses the universal artifact frontmatter schema plus plan provenance extensions defined in the repository's artifact conventions. The fields are generated by running the resolve-frontmatter.sh script with the plan-mode skill flag.

Can I create a ticket after saving a plan?

Yes. After saving, the skill prompts you to create or update a ticket for the work using the create-ticket skill, and presents next-step options in the same completion message.

What happens if no plan exists in the conversation?

The skill extracts the most recent plan discussed or produced in the conversation context, so it requires a prior planning discussion or plan mode output. Without one, there is no plan content to save as an artifact.