Create an implementation plan from a ticket or task description.
npx skills add https://github.com/williamthorsen/codeassembly --skill plan-williamthorsen
Please help me install this Agent Skill. Skill: plan Source: https://github.com/williamthorsen/codeassembly/tree/main/packages/agents/content/skills/plan Command: npx skills add https://github.com/williamthorsen/codeassembly --skill plan-williamthorsen
#99, a file path, or a free-form description of what to build. - Standardized plan output: Produces a plan with canonical YAML frontmatter and a shared implementation-plan template, identical to the plan phase of design-and-plan. - Context-aware saving: Saves the plan as a run artifact inside an active run or as a ticket-level artifact derived from session context, with timestamped naming conventions. - Use Case: Given a GitHub issue URL describing a migration task, generate a step-by-step implementation plan with risks and unknowns called out, saved to the ticket's artifact directory. ## Quick Start Ask the agent to create an implementation plan from issue #99 or from a description of the feature you want to build.High-intent search queries and answers about installing and using this skill.
Pass the issue URL or a shorthand reference like #99 as the task source. The skill resolves the source, reads the ticket, and generates a structured implementation plan saved as a timestamped markdown artifact.
The plan skill is the standalone plan-phase entry point that skips interactive design exploration. The design-and-plan skill runs a design phase with ticket refinement first, then executes the same plan phase, producing an identical plan template.
Yes, the task source can be a plain description of what to build. The skill plans directly from the description, and the ticket path is omitted from follow-up options since no ticket exists.
Inside an active run it saves as a run artifact named with timestamp and role. Otherwise it derives session context to save a ticket-level artifact under the project's ticket directory using the format {YYYYMMDD-HHMMSSZ}_{slug}_plan.md.
Avoid it when the ticket still needs interactive design exploration or refinement; use design-and-plan instead. The plan skill does not run staleness checks or design Q&A, so it assumes the source ticket is already well-formed.
Brave-LabsCreate GitHub, Linear, or JIRA tickets with structured titles, descriptions, and labels.
crbnosExecutes approved implementation plans task by task with per-task verification and commits.
yashs33244Save git state and session summaries into gstack-managed artifacts.
marcusrbrownGuide discovery, exploration, and design capture before planning.