pencil-to-openspec

To convert a Pencil prototype into OpenSpec requirements, you parse the .pen JSON file to generate proposal.md, capability-based spec.md files, and tasks.md using SHALL/MUST language and WHEN/THEN scenarios. This automates design-to-dev handoff without manual rewriting.

Generating acceptance scenarios from UI frames involves mapping multiple page states and reusable components from a .pen prototype into an OpenSpec change proposal. It captures stateful behavior across frames using a WHEN/THEN scenario structure to ensure comprehensive coverage.

Yes, you can generate implementation tasks directly from a .pen file by placing it under docs/design/ and running the conversion. It produces a tasks plan covering routes, components, styling, and integration ready for engineering handoff or openspec-to-code.

The design to dev handoff process can create or use an existing openspec workspace. It writes the generated proposal.md, per-capability specs, and tasks.md directly under openspec/changes/{change-id} to maintain organized change tracking.

Extracted elements from a Pencil prototype include frames, tokens, components, text, icons, layout patterns, and interactive elements. These visual components are mapped into coherent capabilities to align UI design with structured OpenSpec specifications.