/euxlab-setup
you invokewrites docs/agents/engagement.md
Configure one engagement and write the folder scaffold.
When you reach for it
A new engagement has started and nothing else in the suite works yet. The skills are a flow with shared state, and this is what writes the state. Run it once, inside the engagement folder, before any other skill.
Input, output, writes
- Input
- What you know about the client, the domain, the design system, and the consent posture.
- Output
- A filled engagement file, a glossary stub, and the folder scaffold every other skill reads.
- Writes
- docs/agents/engagement.md
Completion criterion
docs/agents/engagement.md exists with every section filled or explicitly marked not yet known, the folder scaffold matches the tree, and the consent posture names a retention period and an identification scheme. A blank field is allowed; a missing section is not.
Checkable, and demanding. A skill that cannot say whether it is finished is a prompt.
Anti-patterns
- Guessing at the consent posture instead of marking it `not yet known` and asking.
- Running it outside the engagement folder, which scatters state across two trees.