Prompt-to-project intake workflow
How a new Hyphenomenon project starts with one operator prompt that names the intake skill, local repo path, project title, and route context, then becomes a reviewable project page, workflow record, notes, screenshots, and graph membership through scaffold, hydration, dry-run, and human approval.
Workflow steps
- 1
Apply approved evidence to the local knowledge backbone without unreviewed production mutation
Action
- 2
Capture route screenshots and inspect source files, docs, scripts, and existing project governance for usable proof
Action
- 3
Fill the dossier with source-backed project context, candidate nodes, relationships, and explicit exclusions
Process
- 4
Run project and workflow dry-runs to inspect packet quality, database deltas, member refs, media, edges, and guard failures before any apply
Action
- 5
Extract curated source artifacts into hydrated note candidates with provenance and avoid screenshot-gallery or operator-exhaust notes
Action
- 6
Operator prompts Codex to run the Hyphenomenon intake skill with project title, local repo path, source paths, live URL, and canonical route
Action
- 7
Create project-page and workflow packets that translate the dossier into public sections, artifact notes, workflow steps, and graph links
Process
- 8
Render the public project page, workflow route, supporting notes, and Explore map membership
State
- 9
Human operator decides whether the generated record is clear enough to apply locally, append evidence only, rewrite, or stop
Decision
- 10
Skill scaffolds the intake dossier and screenshot folder so the project has a repeatable evidence package
Process