Summary
Please consider adding a DESIGN_PLAN_PATH environment variable that lets a caller configure where DESIGN_PLAN.md is written, mirroring the existing configurability of DESIGN_MEMORY.md (DESIGN_MEMORY_PATH).
Motivation
The README's "No mess left behind" principle is exactly why this would help downstream integrations. design-lab is composed by other frameworks, and a configurable output path lets those frameworks keep a project's repo root clean by routing DESIGN_PLAN.md into a managed subfolder rather than dropping it at the root.
Concretely, I maintain ux-agent-skills, which composes the design-lab skill. It relocates framework-managed state into a single .ux/ hub so nothing colonizes the user's repo root. Today I can set DESIGN_MEMORY_PATH to route the memory file, but there is no equivalent for DESIGN_PLAN.md, so I have to move it after the run. An env var would make the handoff fully in-place and symmetric.
Proposed behavior
DESIGN_PLAN_PATH — when set, write the finalized DESIGN_PLAN.md to this path instead of the repo root.- Unset → current behavior (root
DESIGN_PLAN.md), so this is fully backward-compatible.
Symmetry with DESIGN_MEMORY_PATH keeps the two configurable outputs consistent. Happy to help test or send a PR if that's useful. Thanks for the skill!
Summary
Please consider adding a
DESIGN_PLAN_PATHenvironment variable that lets a caller configure whereDESIGN_PLAN.mdis written, mirroring the existing configurability ofDESIGN_MEMORY.md(DESIGN_MEMORY_PATH).Motivation
The README's "No mess left behind" principle is exactly why this would help downstream integrations.
design-labis composed by other frameworks, and a configurable output path lets those frameworks keep a project's repo root clean by routingDESIGN_PLAN.mdinto a managed subfolder rather than dropping it at the root.Concretely, I maintain
ux-agent-skills, which composes thedesign-labskill. It relocates framework-managed state into a single.ux/hub so nothing colonizes the user's repo root. Today I can setDESIGN_MEMORY_PATHto route the memory file, but there is no equivalent forDESIGN_PLAN.md, so I have to move it after the run. An env var would make the handoff fully in-place and symmetric.Proposed behavior
DESIGN_PLAN_PATH— when set, write the finalizedDESIGN_PLAN.mdto this path instead of the repo root.DESIGN_PLAN.md), so this is fully backward-compatible.Symmetry with
DESIGN_MEMORY_PATHkeeps the two configurable outputs consistent. Happy to help test or send a PR if that's useful. Thanks for the skill!