Workflows are readable paths for moving work from one state to another. They are useful when the process still needs judgment, crosses roles, or should stay visible as a shared operating method.
If you are new here, start with Idea to publish. It is the clearest example of how RomeoRaven turns a rough thought into public material without losing the review steps that keep the site useful.
RomeoRaven uses workflows beside skills. A workflow explains the path. A skill packages a repeatable behavior once the pattern is stable enough to trigger and reuse consistently.
Idea to publish
The path from rough source material to a reviewed public page.
Reference layerKnowledge Base
Reusable definitions and workflow references belong in the KB when they need durable detail.
Companion areaSkills
Stable reusable behaviors sit beside workflows when a pattern becomes packaged.
Operating contextSystems
Systems show where workflows fit inside broader site, content, and coordination work.
Current Workflow Areas
| Area | Purpose | State |
|---|---|---|
| Idea to publish | Move public content from rough idea through shaping, preview, and approval. | Public page. |
| North Star to roadmap | Turn a broad site or initiative direction into phases, gates, and build slices. | Active as the RR planning path. |
| Roadmap phase blueprint | Break one roadmap phase into buildable action slices with validation. | Active as the current RR implementation path. |
| Preview to publish | Keep preview review separate from public publishing. | Active rule; public publish remains approval-gated. |
What A Public Workflow Should Include
- When to use it.
- What context it starts from.
- What roles or responsibilities are involved.
- What output it creates.
- What proof or review is required.
- What feedback should improve the workflow after use.
Current State
This route is the public workflow hub. It starts with the content path that keeps launch work from turning private notes into public copy by accident.