@xenonbyte/da-vinci-workflow 0.1.2

package/commands/claude/da-vinci.md

@@ -0,0 +1,23 @@
+---
+description: Da Vinci workflow command index for Claude
+---
+# Da Vinci
+
+Use the `da-vinci` skill for this request.
+
+Platform: Claude
+Default workflow entry: `/da-vinci <request>`
+
+Available routes:
+- `/dv:breakdown` - Break a product or page request into scope, flows, states, and requirements.
+- `/dv:design` - Plan or create Pencil-backed page designs from approved requirements.
+- `/dv:tasks` - Generate implementation tasks from requirements plus Pencil design coverage.
+- `/dv:build` - Implement code that follows both the requirements and the Pencil design.
+- `/dv:verify` - Check requirement coverage, design coverage, and implementation drift.
+
+Notes:
+- Requirements decide behavior.
+- Pencil decides presentation.
+- Code must follow both.
+- Use `references/platform-adapters.md` for shared invocation rules.
+- Use `references/checkpoints.md` when running workflow checkpoints.

package/commands/claude/dv/breakdown.md

@@ -0,0 +1,21 @@
+---
+description: Break requirements into scope, flows, states, and specs for Da Vinci.
+---
+# Da Vinci Breakdown
+
+Use the `da-vinci` skill for this request.
+
+Action: `breakdown`
+
+Focus on:
+- scope
+- pages
+- flows
+- states
+- data and integration needs
+
+Create or update:
+- `proposal.md`
+- `specs/<capability>/spec.md`
+
+Ask only the minimum clarification needed to define implementation-safe requirements.

package/commands/claude/dv/build.md

@@ -0,0 +1,17 @@
+---
+description: Build software from requirements and Pencil design data for Da Vinci.
+---
+# Da Vinci Build
+
+Use the `da-vinci` skill for this request.
+
+Action: `build`
+
+Focus on:
+- requirements-backed behavior
+- Pencil-backed layout and presentation
+- implementation order from `tasks.md`
+
+During implementation:
+- run `execution checkpoint` after each top-level task group
+- update source artifacts before continuing if drift is found

package/commands/claude/dv/design.md

@@ -0,0 +1,20 @@
+---
+description: Create or refine Pencil-backed design plans for Da Vinci.
+---
+# Da Vinci Design
+
+Use the `da-vinci` skill for this request.
+
+Action: `design`
+
+Focus on:
+- page map
+- layout structure
+- interaction model
+- Pencil page coverage
+
+Create or update:
+- `design.md`
+- `pencil-design.md`
+
+Run the `design checkpoint` before locking implementation tasks.

package/commands/claude/dv/tasks.md

@@ -0,0 +1,19 @@
+---
+description: Generate implementation tasks from requirements and Pencil designs for Da Vinci.
+---
+# Da Vinci Tasks
+
+Use the `da-vinci` skill for this request.
+
+Action: `tasks`
+
+Focus on:
+- top-level task groups
+- spec coverage
+- Pencil coverage
+- dependency order
+
+Create or update:
+- `tasks.md`
+
+Run the `task checkpoint` before implementation begins.

package/commands/claude/dv/verify.md

@@ -0,0 +1,16 @@
+---
+description: Verify requirement coverage, Pencil coverage, and drift for Da Vinci.
+---
+# Da Vinci Verify
+
+Use the `da-vinci` skill for this request.
+
+Action: `verify`
+
+Check:
+- behavior coverage against specs
+- page and section coverage against Pencil
+- drift between requirements, Pencil, tasks, and code
+
+Create or update:
+- `verification.md`

package/commands/codex/prompts/da-vinci.md

@@ -0,0 +1,24 @@
+---
+description: Da Vinci entrypoint for Codex. Prefer the da-vinci skill for natural-language workflow requests.
+---
+# Da Vinci
+
+Use the `da-vinci` skill for this request.
+
+Codex usage model:
+- Preferred: `$da-vinci <request>`
+- Explicit routing: `/prompts:da-vinci` and `/prompts:dv-*`
+
+Available routes:
+- `/prompts:dv-breakdown` - Break a request into requirements, pages, flows, and states.
+- `/prompts:dv-design` - Plan or create Pencil-backed designs from approved requirements.
+- `/prompts:dv-tasks` - Generate implementation tasks from requirements plus Pencil.
+- `/prompts:dv-build` - Implement code from requirements plus Pencil data.
+- `/prompts:dv-verify` - Verify requirement coverage, design coverage, and drift.
+
+Important:
+- Treat `/prompts:*` as action selectors in Codex.
+- If details are still needed after route selection, provide them in the next message.
+- Requirements decide behavior.
+- Pencil decides presentation.
+- Code must follow both.

package/commands/codex/prompts/dv-breakdown.md

@@ -0,0 +1,19 @@
+---
+description: Da Vinci breakdown route for Codex.
+---
+# Da Vinci Breakdown
+
+Use the `da-vinci` skill for this request.
+
+Action: `breakdown`
+
+Output should move the work toward:
+- `proposal.md`
+- `specs/<capability>/spec.md`
+
+Break the request into:
+- scope
+- pages
+- flows
+- states
+- data needs

package/commands/codex/prompts/dv-build.md

@@ -0,0 +1,13 @@
+---
+description: Da Vinci build route for Codex.
+---
+# Da Vinci Build
+
+Use the `da-vinci` skill for this request.
+
+Action: `build`
+
+Implementation rules:
+- requirements decide behavior
+- Pencil decides presentation
+- run `execution checkpoint` after each top-level task group

package/commands/codex/prompts/dv-design.md

@@ -0,0 +1,14 @@
+---
+description: Da Vinci design route for Codex.
+---
+# Da Vinci Design
+
+Use the `da-vinci` skill for this request.
+
+Action: `design`
+
+Output should move the work toward:
+- `design.md`
+- `pencil-design.md`
+
+Use Pencil-backed structure as the design source when available.

package/commands/codex/prompts/dv-tasks.md

@@ -0,0 +1,16 @@
+---
+description: Da Vinci tasks route for Codex.
+---
+# Da Vinci Tasks
+
+Use the `da-vinci` skill for this request.
+
+Action: `tasks`
+
+Output should move the work toward:
+- `tasks.md`
+
+Tasks must cover:
+- spec-backed behavior
+- Pencil-backed UI work
+- verification work

package/commands/codex/prompts/dv-verify.md

@@ -0,0 +1,15 @@
+---
+description: Da Vinci verify route for Codex.
+---
+# Da Vinci Verify
+
+Use the `da-vinci` skill for this request.
+
+Action: `verify`
+
+Check:
+- requirement coverage
+- Pencil coverage
+- drift between artifacts and code
+
+Update `verification.md` when needed.

package/commands/gemini/da-vinci.toml

@@ -0,0 +1,26 @@
+description = "Da Vinci workflow command index for Gemini"
+prompt = """
+---
+description: Da Vinci workflow command index for Gemini
+---
+# Da Vinci
+
+Use the `da-vinci` skill for this request.
+
+Platform: Gemini
+Default workflow entry: `/da-vinci <request>`
+
+Available routes:
+- `/dv:breakdown` - Break a product or page request into scope, flows, states, and requirements.
+- `/dv:design` - Plan or create Pencil-backed page designs from approved requirements.
+- `/dv:tasks` - Generate implementation tasks from requirements plus Pencil design coverage.
+- `/dv:build` - Implement code that follows both the requirements and the Pencil design.
+- `/dv:verify` - Check requirement coverage, design coverage, and implementation drift.
+
+Notes:
+- Requirements decide behavior.
+- Pencil decides presentation.
+- Code must follow both.
+- Keep workflow semantics shared across Claude, Codex, and Gemini.
+
+"""

package/commands/gemini/dv/breakdown.toml

@@ -0,0 +1,19 @@
+description = "Break requirements into scope, flows, states, and specs for Da Vinci."
+prompt = """
+# Da Vinci Breakdown
+
+Use the `da-vinci` skill for this request.
+
+Action: `breakdown`
+
+Focus on:
+- scope
+- pages
+- flows
+- states
+- data and integration needs
+
+Create or update:
+- `proposal.md`
+- `specs/<capability>/spec.md`
+"""

package/commands/gemini/dv/build.toml

@@ -0,0 +1,13 @@
+description = "Build software from requirements and Pencil design data for Da Vinci."
+prompt = """
+# Da Vinci Build
+
+Use the `da-vinci` skill for this request.
+
+Action: `build`
+
+Implementation rules:
+- requirements decide behavior
+- Pencil decides presentation
+- run `execution checkpoint` after each top-level task group
+"""

package/commands/gemini/dv/design.toml

@@ -0,0 +1,14 @@
+description = "Create or refine Pencil-backed design plans for Da Vinci."
+prompt = """
+# Da Vinci Design
+
+Use the `da-vinci` skill for this request.
+
+Action: `design`
+
+Create or update:
+- `design.md`
+- `pencil-design.md`
+
+Use Pencil-backed page coverage as the source of presentation truth.
+"""

package/commands/gemini/dv/tasks.toml

@@ -0,0 +1,13 @@
+description = "Generate implementation tasks from requirements and Pencil designs for Da Vinci."
+prompt = """
+# Da Vinci Tasks
+
+Use the `da-vinci` skill for this request.
+
+Action: `tasks`
+
+Create or update:
+- `tasks.md`
+
+Tasks must cover spec behavior, Pencil-backed UI work, and verification.
+"""

package/commands/gemini/dv/verify.toml

@@ -0,0 +1,15 @@
+description = "Verify requirement coverage, Pencil coverage, and drift for Da Vinci."
+prompt = """
+# Da Vinci Verify
+
+Use the `da-vinci` skill for this request.
+
+Action: `verify`
+
+Check:
+- requirement coverage
+- Pencil coverage
+- drift between artifacts and code
+
+Update `verification.md` when needed.
+"""

package/docs/workflow-examples.md

@@ -0,0 +1,104 @@
+# Workflow Examples
+
+These examples show how to use Da Vinci in each supported workflow mode.
+
+## 1. `greenfield-spec`
+
+Use when a new project already has a stable requirement set.
+
+Example request:
+
+```text
+$da-vinci use greenfield-spec to break down a new desktop software project for annotated design delivery
+```
+
+Expected flow:
+
+1. create `design-brief.md`
+2. create `proposal.md`
+3. create `specs/<capability>/spec.md`
+4. create `page-map.md`
+5. register `.pen` sources in `design-registry.md`
+6. create Pencil pages and record them in `pencil-design.md`
+7. bind implementation pages in `pencil-bindings.md`
+8. generate `tasks.md`
+9. build and verify
+
+## 2. `greenfield-brainstorm`
+
+Use when the project starts from multiple rounds of rough ideas.
+
+Example request:
+
+```text
+$da-vinci use greenfield-brainstorm to turn product brainstorming into a page map, Pencil design plan, and implementation tasks
+```
+
+Expected flow:
+
+1. synthesize ideas into `brainstorm.md`
+2. capture product form factor and preferences in `design-brief.md`
+3. stabilize scope in `proposal.md`
+4. write behavior in `specs/<capability>/spec.md`
+5. define pages in `page-map.md`
+6. register and generate Pencil sources
+7. bind implementation pages to Pencil pages
+8. generate tasks
+9. build and verify
+
+## 3. `redesign-from-code`
+
+Use when the current product already exists and the UI needs broad redesign.
+
+Example request:
+
+```text
+$da-vinci use redesign-from-code to inventory the current app, identify current pages, and generate a new Pencil-backed redesign plan
+```
+
+Expected flow:
+
+1. scan the existing product into `project-inventory.md`
+2. register any current `.pen` sources in `design-registry.md`
+3. define redesign scope in `proposal.md`
+4. write redesign constraints in `specs/<capability>/spec.md`
+5. rebuild or refine `page-map.md`
+6. create new or updated Pencil pages
+7. bind routes and pages to Pencil screens
+8. generate tasks
+9. build and verify
+
+## 4. `feature-change`
+
+Use when an existing product needs a scoped requirement or page change.
+
+Example request:
+
+```text
+$da-vinci use feature-change to add a billing page, generate the Pencil design delta, and create implementation tasks
+```
+
+Expected flow:
+
+1. define the change in `proposal.md`
+2. write affected behavior in `specs/<capability>/spec.md`
+3. update the affected subset of `page-map.md`
+4. reuse or update the active design source in `design-registry.md`
+5. create the Pencil delta in `pencil-design.md`
+6. update `pencil-bindings.md`
+7. generate tasks
+8. build and verify
+
+## Cross-mode rule
+
+In every mode:
+
+- requirements decide behavior
+- Pencil decides presentation
+- code follows both
+
+And in every mode:
+
+- `design-registry.md` tracks the available `.pen` sources
+- `pencil-bindings.md` tracks implementation page to Pencil page mapping
+- the workflow runs as `autonomous-by-default` unless a real blocker exists

package/examples/greenfield-spec-markupflow/README.md

@@ -0,0 +1,40 @@
+# MarkupFlow Forward Test
+
+This example is a repo-local end-to-end forward test for Da Vinci.
+
+Mode:
+
+- `greenfield-spec`
+
+Scenario:
+
+- a desktop-software product named `MarkupFlow`
+- two launch pages
+- Pencil-backed design source
+- static `HTML + Tailwind` implementation
+
+Files in this example:
+
+- `design-brief.md`
+- `proposal.md`
+- `specs/marketing-site/spec.md`
+- `page-map.md`
+- `design.md`
+- `design-registry.md`
+- `pencil-design.md`
+- `pencil-bindings.md`
+- `tasks.md`
+- `verification.md`
+- `site/index.html`
+- `site/product-detail.html`
+
+Live design source used for this forward test:
+
+- active Pencil document: `pencil-new.pen`
+- homepage screen: `MarkupFlow Homepage` (`bi8Au`)
+- detail screen: `MarkupFlow Product Detail` (`LpyYx`)
+
+Important note:
+
+- the `.pen` source was authored in a live Pencil session and is not committed into this repository
+- this example records the design source and bindings explicitly so implementation can still trace back to the correct Pencil pages

package/examples/greenfield-spec-markupflow/design-brief.md

@@ -0,0 +1,24 @@
+# Design Brief
+
+## Product Form Factor
+- desktop software product
+- desktop-first marketing pages for launch and product explanation
+
+## Visual Direction
+- dark product-marketing surface
+- high-contrast hero
+- tool-like presentation instead of generic SaaS cards
+
+## Brand Constraints
+- product name: `MarkupFlow`
+- modern technical tone
+- strong emphasis on annotated design delivery and MCP readiness
+
+## Layout Priorities
+- desktop-first composition
+- wide hero with product-flow preview
+- clear sectioning for capabilities, workflow, and CTA
+
+## Notes
+- inferred from the requested scenario: HTML to annotated design, Figma to annotated design, annotated design as MCP data source
+- the example keeps mobile responsive behavior minimal and focuses on desktop fidelity

package/examples/greenfield-spec-markupflow/design-registry.md

@@ -0,0 +1,15 @@
+# Design Registry
+
+## Active Design Sources
+- `pencil-new.pen` -> active -> live authoring source used for the forward test homepage and detail page
+
+## Preferred Design Source
+- `pencil-new.pen`
+- reason: it is the source used to create the current implementation outputs
+
+## Historical Or Secondary Sources
+- none recorded for this forward test
+
+## Notes
+- the source was authored in an active Pencil session and was not exported into this repository
+- traceability is preserved through stable screen names and screen ids in `pencil-design.md` and `pencil-bindings.md`

package/examples/greenfield-spec-markupflow/design.md

@@ -0,0 +1,32 @@
+# Design
+
+## Page Map
+- the homepage is a high-impact launch page with a left text column and a right product-flow preview
+- the product detail page is a workflow explanation page with a desktop-workspace hero and a structured pipeline section
+
+## Interaction Model
+- primary CTA on the homepage points users toward product evaluation
+- homepage secondary CTA moves to the product detail page
+- product detail page explains the editor pipeline rather than adding new navigation complexity
+
+## Layout Strategy
+- desktop-first sections
+- large hero headlines
+- dark interface shell with occasional light contrast panels for emphasis
+- modular sections with strong content hierarchy
+
+## Component Strategy
+- shared header treatment across both pages
+- recurring dark panel cards for workflow and capability explanation
+- one light contrast content panel per page to signal structured output
+
+## Content Notes
+- keep copy direct and product-oriented
+- repeat the three-part product thesis consistently:
+  - import from HTML or Figma
+  - annotate into a structured design artifact
+  - publish MCP-ready design data
+
+## Open Questions
+- whether the repo should eventually commit the `.pen` file instead of only recording the active Pencil source
+- whether future iterations should split the product detail page into workflow and MCP integration pages

package/examples/greenfield-spec-markupflow/page-map.md

@@ -0,0 +1,19 @@
+# Page Map
+
+## Canonical Pages
+- `Homepage` -> `/` -> launch overview for the desktop product and its three core capabilities
+- `Product Detail` -> `/product-detail.html` -> deeper explanation of the workflow, workspace, and MCP publishing model
+
+## States Per Page
+- `Homepage`: default marketing state
+- `Product Detail`: default product-explanation state
+
+## Shared Sections
+- product header
+- desktop-product positioning line
+- terminal CTA section
+
+## Page Priority
+- core pages:
+  - `Homepage`
+  - `Product Detail`

package/examples/greenfield-spec-markupflow/pencil-bindings.md

@@ -0,0 +1,13 @@
+# Pencil Bindings
+
+## Page To Pencil Page
+- `/` -> `pencil-new.pen` -> `MarkupFlow Homepage` (`bi8Au`)
+- `/product-detail.html` -> `pencil-new.pen` -> `MarkupFlow Product Detail` (`LpyYx`)
+
+## Shared Regions
+- `Site header` -> shared header treatment represented in both screens
+- `Closing CTA band` -> shared end-of-page CTA treatment represented in both screens
+
+## Notes
+- this forward test uses one live `.pen` source with two implementation pages
+- if the Pencil source is exported to the repository later, update the source path here and keep the same screen names where possible

package/examples/greenfield-spec-markupflow/pencil-design.md

@@ -0,0 +1,29 @@
+# Pencil Design
+
+## Active `.pen` Source
+- `pencil-new.pen`
+
+## Screens
+- `MarkupFlow Homepage` -> screen id `bi8Au`
+- `MarkupFlow Product Detail` -> screen id `LpyYx`
+
+## Screen Notes
+- the homepage screen contains:
+  - hero
+  - capabilities
+  - MCP service
+  - closing CTA
+- the product detail screen contains:
+  - desktop workspace hero
+  - three-step pipeline
+  - workspace modules
+  - closing CTA
+
+## Implementation Notes
+- preserve the dark desktop-software visual language
+- keep the structural emphasis on three core capabilities on page one
+- keep the import, annotate, publish pipeline readable on page two
+
+## Validation Notes
+- both screens were reviewed in Pencil during authoring
+- no obvious clipping, overlap, or alignment failures were observed in the design pass

package/examples/greenfield-spec-markupflow/proposal.md

@@ -0,0 +1,33 @@
+# Proposal
+
+## Change
+- Name: MarkupFlow launch pages
+- Owner: Da Vinci forward test
+- Date: 2026-03-27
+
+## Goal
+- deliver a two-page launch surface for a desktop software product that converts HTML and Figma sources into annotated design output and exposes structured MCP data
+
+## Non-Goals
+- account system
+- pricing logic
+- dashboard implementation
+- API integration
+
+## User Value
+- a buyer or evaluator can understand the product capability, workflow, and delivery model in two pages
+
+## Scope
+- homepage
+- product detail page
+- cross-page navigation
+- static launch-page implementation
+
+## Risks
+- the `.pen` source exists in a live Pencil session instead of a committed repository file
+- design-source traceability must rely on explicit screen identifiers
+
+## Success Criteria
+- both pages exist in the repo as static deliverables
+- each implementation page is bound to a named Pencil page
+- verification can show requirement coverage and design coverage without unresolved drift