HeyEddi-com HeyEddi Setup
Project working agreement for agents: ensure .heyeddi/stack.json has git/env + agent prefs. Re-run anytime to update.
Always on as the prefs hard gate before git/CI/commit/push or agent autonomy. See reference/setup-always-on.md and hub docs/always-on-skills.md.
Does not quiz frontend, backends, package manager, or CI — those are filled by scaffold / engineering / CI skills as the project evolves.
When to use
- Missing
git/agent/setupprefs instack.json - User says "setup", "preferences", or
@heyeddi-setup - Session start when
verify_setup --checkfails (hard route — do not invent prefs) - Before commit, push, PR base, or branch/env assumptions
- Re-run to change env layout or agent autonomy
Hard gate
python .agents/skills/heyeddi-setup/scripts/verify_setup.py --project-root . --check
- Exit 0 — honor prefs in
stack.json - Exit 1 — stop git/CI/agent assumptions; finish this skill until check passes
Non-git work may continue. Never invent branch names, PR bases, or auto-commit/push while incomplete.
Mandatory pipeline
load_setup— currentstack.json+missingpathslist_questions— ask all on re-run;--missing-onlyon first pass OK- Ask the user (defaults shown)
write_setup --json '…'verify_setup --check— must pass before you stop
Questions (prefs only)
| # | Ask | Choices |
|---|---|---|
| 1 | Env / branch layout? | main_staging_dev (default) or main_dev |
| 2 | Different workflow? | no → keep preset; or describe (gitflow, trunk+tags, …) → custom |
| 3 | Git worktrees for parallel features? | yes / no |
| 4 | Agent may commit without asking? | ask / auto |
| 5 | Agent may push without asking? | ask / auto |
Presets (always production + staging)
| Preset | Mapping |
|---|---|
main_staging_dev |
prod ← main, staging ← staging, dev ← dev; pr_base = dev |
main_dev |
prod ← main, staging ← dev; pr_base = dev |
Tools
python .agents/skills/heyeddi-setup/scripts/load_setup.py --project-root .
python .agents/skills/heyeddi-setup/scripts/list_questions.py --project-root .
python .agents/skills/heyeddi-setup/scripts/write_setup.py --project-root . --json '{"git.preset":"main_staging_dev","git.custom_workflow":null,"git.worktrees":false,"agent.commit":"ask","agent.push":"ask"}'
python .agents/skills/heyeddi-setup/scripts/verify_setup.py --project-root . --check
Agents: always honor prefs
Read .heyeddi/stack.json before git/commit/push (only after verify_setup --check passes):
git.environments— which branch maps to production / staging / (optional) devgit.pr_base/git.default_branchgit.custom_workflow— if set, follow that description over the presetagent.commit/agent.push— ifask, confirm first
Never
- Ask frontend / backends / package manager / CI in this skill
- Put prefs outside
.heyeddi/stack.json - Claim setup done without
verify_setup --check - Treat incomplete prefs as advisory when about to commit, push, or assume branches
- Replace
@project-engineering/@flutter-engineeringscaffold duties
When the task is complete: suggest next skills
python .agents/skills/heyeddi-orchestrator/scripts/suggest_next_skill.py --current-skill heyeddi-setup --project-root .
Include the script's ### Next step block in your final reply.
Related
reference/setup-always-on.md— hard gate policyreference/stack-schema.md— key list@heyeddi-orchestrator— hard-route setup when prefs incomplete@pre-merge-gate— runsverify_setup --check@project-engineering/@flutter-engineering— discover and write tech intostack.json