design-and-plan

Guides interactive design exploration to produce a refined ticket and implementation plan.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a vague task, issue, or idea into an actionable engineering ticket and implementation plan requires structured exploration that ad-hoc prompting rarely delivers. This Skill walks through requirements gathering, design convergence, ticket refinement, and plan generation so a competent coder receives everything needed to implement the work. ## Core Features & Use Cases - Interactive design exploration: Asks clarifying questions one at a time, proposes 2-3 approaches with trade-offs when the solution is not obvious, and requires explicit approval before moving forward. - Ticket staleness detection: Counts commits since a remote ticket's last update and optionally runs a drift assessment to verify the ticket is still relevant. - Dual artifact output: Produces a refined ticket and an implementation plan saved with timestamped names and universal frontmatter, with an optional consented update back to the remote issue. - Use Case: Given a GitHub issue URL describing a new feature, the Skill explores the codebase, asks targeted questions, converges on a design, rewrites the ticket with acceptance criteria, and generates a step-by-step implementation plan. ## Quick Start Ask the agent to run the design-and-plan skill on a GitHub issue URL or a description of the feature you want to build.

Frequently Asked Questions about design-and-plan

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

FAQPage Schema
How do I turn a GitHub issue into an implementation plan?

Provide the issue URL or shorthand reference as the task source. The skill resolves the ticket, explores requirements through one-at-a-time questions, converges on a design with your approval, refines the ticket, and then generates the implementation plan as a saved artifact.

How does ticket staleness detection work before planning?

The skill compares the ticket's last-updated date against the count of commits made since then using git rev-list. If the ticket is older than 3 days and more than 5 commits have landed, it offers a drift assessment; you can force or skip this with --check-staleness or --skip-staleness.

Can I generate only an implementation plan without the design phase?

Yes. When the ticket is already well-formed and only the plan is needed, run the standalone plan skill directly. The design-and-plan skill produces the same plan from a shared template but includes the interactive design and ticket refinement phases first.

Does the skill update the remote GitHub issue automatically?

No. It offers to write the refined ticket back to the remote issue only when the source was a remote ticket and the refined body differs from it. The update requires your explicit consent and replaces the remote body outright.

What artifacts does the design and plan workflow produce?

It saves two Markdown artifacts: a refined ticket and an implementation plan, named with timestamps and stored under a project and ticket ID directory. Both carry universal frontmatter resolved by a helper script, and their paths are reported at completion.