Skip to content
This repository was archived by the owner on Aug 10, 2026. It is now read-only.

Repository files navigation

design-workflow

Archived — 2026-08-10

This project is no longer maintained. Development has been discontinued because the surrounding design-agent ecosystem now provides a more appropriate execution and plugin substrate, making the original standalone direction no longer worth maintaining.

The repository is preserved for historical reference only. Existing releases remain available as-is, but no further features, fixes, compatibility work, or releases are planned.

Status

  • Maintenance: discontinued
  • New features: not planned
  • Bug fixes: not planned
  • New releases: not planned
  • Existing code and releases: retained for reference

Open work has been closed as not planned.

Historical purpose

design-workflow was a portable Agent Skill for deciding what should stay fixed, what could change, and whether a visual artifact should be preserved, expanded, created, or explicitly redesigned before an execution tool performed the actual work.

Its main ideas included:

  • preserve / expand / create / redesign routing;
  • meaningful_design_exists as a boundary signal;
  • fixed vs. changeable design dimensions;
  • evidence and provenance requirements;
  • anti-template / authoredness checks;
  • bounded critique and repair;
  • deterministic packaging and validation.

The repository remains available so those ideas, tests, and implementation history can still be inspected or reused under the existing license.

License

Apache-2.0. See the repository license and provenance files for details.

About

No description, website, or topics provided.

Resources

Contributing

Security policy

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages