What problem does it solve? Setting up a Hall9k project or node requires a consistent, machine-specific orchestrator recipe: the prompts and seed files that let a human launch a disposable orchestrator session from a terminal. Writing these by hand risks drift, invented rules, and guessed facts about the machine or platform. ## Core Features & Use Cases - Dual-mode generation: Runs in project mode (resolved via h9k project show) or node mode (resolved via h9k config show), each producing its own recipe set. - Observed-fact discovery: Inspects the OS, shell, daemon log path, agent CLIs, concurrency ceiling, budget, and registered projects through h9k CLI commands rather than assumptions. - Safe regeneration: Never overwrites existing recipes; writes .new siblings for reconciliation, seeds journal.md, sessions.md, and background log-waiter scripts only when absent. - Use Case: After installing Hall9k on a new machine or registering a new project, run this Skill to produce recipes/orchestrator.md, scoped-session recipes, and a byte-offset polling waiter script tailored to that machine's shell and log paths. ## Quick Start Ask the agent to run the orchestrator-recipe-generator skill to generate this project's orchestrator recipe from its home directory.
