@starlein/paperclip-plugin-company-wizard 0.2.1

package/templates/presets/build-game/preset.meta.json

@@ -0,0 +1,150 @@
+{
+  "name": "build-game",
+  "description": "Build a game from idea to playable release. Game design, prototyping, art creation, playtesting, and shipping. Works for any genre — platformers, puzzles, roguelikes, strategy, etc.",
+  "constraints": [],
+  "roles": [
+    "engineer",
+    "game-designer",
+    "game-artist",
+    "audio-designer"
+  ],
+  "modules": [
+    "game-design",
+    "tech-stack",
+    "github-repo",
+    "backlog",
+    "auto-assign",
+    "stall-detection"
+  ],
+  "goals": [
+    {
+      "title": "Build the Game",
+      "description": "Take a game idea from concept to playable release: design the game, prototype the core loop, create art, build all content, playtest, balance, and ship.",
+      "project": true,
+      "subgoals": [
+        {
+          "id": "concept",
+          "title": "Concept",
+          "level": "team",
+          "description": "Define the game: core mechanic, game loop, progression, art direction, and target audience. Done when GDD exists with core mechanic, game loop, progression, controls, art direction, and tuning parameters defined."
+        },
+        {
+          "id": "prototype",
+          "title": "Prototype",
+          "level": "team",
+          "description": "Build a playable prototype of the core loop with placeholder art. Validate that the core mechanic is fun. Done when playable prototype exists with core mechanic implemented and first playtest completed with results documented."
+        },
+        {
+          "id": "vertical-slice",
+          "title": "Vertical Slice",
+          "level": "team",
+          "description": "Polish one complete level or section with production art, audio, and UI. Prove the full experience works. Done when one fully polished level/section playable with final art, UI, and audio, and second playtest round completed."
+        },
+        {
+          "id": "production",
+          "title": "Production",
+          "level": "team",
+          "description": "Build all remaining levels, content, and features. Implement full progression, menus, and game flow. Done when all levels/content built, full game flow works from start screen to end state, and all art assets integrated."
+        },
+        {
+          "id": "polish-ship",
+          "title": "Polish & Ship",
+          "level": "team",
+          "description": "Final balancing, bug fixing, performance optimization, and distribution. Done when game is balanced, bug-free, and distributed to target platform."
+        }
+      ]
+    }
+  ],
+  "issues": [
+    {
+      "title": "Create Game Design Document",
+      "description": "Define the game's complete design. Follow the GDD template in docs/gdd-template.md.\n\nMust include: concept pitch, core mechanic (input → action → feedback → consequence), three-layer game loop, progression system, win/lose conditions, controls, art direction, audio direction, and all tuning parameters.\n\nOutput: docs/GDD.md",
+      "priority": "critical",
+      "assignTo": "game-designer"
+    },
+    {
+      "title": "Choose game engine and set up project",
+      "description": "Based on the GDD requirements (genre, platform, art style), evaluate and select a game engine or framework. Options to consider:\n- **Web:** Phaser, PixiJS, Three.js, Kaboom.js, vanilla Canvas/WebGL\n- **Cross-platform:** Godot, Unity, Love2D, Defold\n- **Minimal:** Custom engine if the game is simple enough\n\nSet up the project structure, build pipeline, and basic game loop scaffold. Document the choice in docs/TECH-STACK.md.",
+      "priority": "critical",
+      "assignTo": "engineer"
+    },
+    {
+      "title": "Define art style guide",
+      "description": "Based on the GDD art direction, create a concrete art style guide:\n- Sprite/asset dimensions and resolution\n- Color palette (exact hex values, limited palette if pixel art)\n- Color language: what colors mean in gameplay (player, enemy, pickup, hazard, background)\n- Animation conventions: frame counts, frame rates, style\n- Asset naming conventions and directory structure\n- Reference images or generated style samples\n\nOutput: docs/ART-STYLE-GUIDE.md and sample assets in assets/reference/",
+      "priority": "high",
+      "assignTo": "game-artist"
+    },
+    {
+      "title": "Approve game concept",
+      "description": "Review the GDD, tech stack choice, and art style guide. Confirm the game direction or request changes before prototype work begins.\n\nCheck:\n- Is the core mechanic clear and implementable?\n- Is the scope realistic?\n- Does the art direction fit the game?\n- Are the platform and engine choices appropriate?",
+      "priority": "high",
+      "assignTo": "user"
+    },
+    {
+      "title": "Implement core mechanic prototype",
+      "description": "Build a playable prototype focused on the core mechanic only:\n- Player character with basic movement and the core action\n- Minimal game loop (start → play → end)\n- Placeholder art (colored rectangles, basic shapes)\n- Tuning parameters exposed as constants (not hardcoded in logic)\n\nThe prototype must be playable and demonstrate whether the core mechanic feels good. Don't build menus, progression, or polish.",
+      "priority": "critical",
+      "assignTo": "engineer"
+    },
+    {
+      "title": "Create placeholder art for prototype",
+      "description": "Generate basic art assets for the prototype:\n- Player character sprite (simple, readable silhouette)\n- Basic tileset or background elements\n- Key interactive objects (enemies, pickups, hazards)\n\nThese are working assets — better than colored rectangles but not final. Focus on gameplay readability over visual polish.",
+      "priority": "high",
+      "assignTo": "game-artist"
+    },
+    {
+      "title": "First playtest and balancing pass",
+      "description": "Play the prototype and document findings:\n- Is the core mechanic fun? Does it feel good?\n- Are controls responsive? Any input lag or awkwardness?\n- Difficulty: too easy, too hard, or unclear?\n- What's missing that would make it fun? What should be cut?\n- Tuning parameter adjustments needed\n\nOutput: docs/PLAYTEST-RESULTS.md with specific findings and recommended changes.",
+      "priority": "high",
+      "assignTo": "game-designer"
+    },
+    {
+      "title": "Create production art for vertical slice",
+      "description": "Generate final-quality art assets for one complete level/section:\n- Player character: full sprite sheet (idle, walk, jump, attack, death animations)\n- Tileset: complete set for one environment type\n- Enemies: sprites with animation frames\n- UI elements: health bar, score display, basic HUD\n- Background layers (if parallax)\n\nFollow the art style guide. Assets must be consistent and game-ready.",
+      "priority": "high",
+      "assignTo": "game-artist"
+    },
+    {
+      "title": "Build polished vertical slice level",
+      "description": "Take one level/section to production quality:\n- Integrate production art assets\n- Implement full game feel: screen shake, hit stop, particles, juice\n- Add UI: HUD, pause menu, game over screen\n- Add sound effects and music (placeholder or generated)\n- Polish: transitions, animations, feedback for every player action\n\nThis level should represent the final game quality.",
+      "priority": "high",
+      "assignTo": "engineer"
+    },
+    {
+      "title": "Design all levels and progression",
+      "description": "Create detailed level designs for the full game:\n- Level-by-level breakdown: layout, encounters, mechanics introduced, difficulty target\n- Progression curve: how difficulty ramps across the full game\n- Unlock schedule: what the player earns and when\n- Pacing map: tension/relief rhythm across the full experience\n\nOutput: docs/LEVEL-DESIGNS.md with per-level specs.",
+      "priority": "high",
+      "assignTo": "game-designer"
+    },
+    {
+      "title": "Create remaining art assets",
+      "description": "Generate all remaining art assets for the full game:\n- Additional tilesets for each environment type\n- All enemy variants with animations\n- Pickups, power-ups, and collectibles\n- Menu screens: title, options, credits\n- Any remaining UI elements\n\nFollow the art style guide. Maintain visual consistency across all assets.",
+      "priority": "high",
+      "assignTo": "game-artist"
+    },
+    {
+      "title": "Build all levels and game flow",
+      "description": "Implement the full game:\n- All levels from the level design document\n- Complete game flow: title screen → level select → gameplay → game over → credits\n- Full progression system: unlocks, saves, scoring\n- All enemy types and behaviors\n- Integrate all art and audio assets\n\nThe game should be completable from start to finish.",
+      "priority": "high",
+      "assignTo": "engineer"
+    },
+    {
+      "title": "Final balancing and bug fixing",
+      "description": "Play through the entire game and:\n- Adjust difficulty curve based on full playthrough\n- Fix all gameplay bugs\n- Tune all parameters for satisfying progression\n- Verify no soft-locks or unwinnable states\n- Check edge cases: max score, empty inventory, rapid inputs\n\nUpdate docs/GDD.md with final tuning values.",
+      "priority": "high",
+      "assignTo": "game-designer"
+    },
+    {
+      "title": "Performance optimization and platform build",
+      "description": "Optimize and prepare for distribution:\n- Performance: stable frame rate on target platform\n- Asset optimization: sprite atlases, compressed textures, lazy loading\n- Build for target platform (web: bundle + deploy, desktop: executable, mobile: package)\n- Test on target devices/browsers\n\nOutput: distributable build in dist/ or build/",
+      "priority": "high",
+      "assignTo": "engineer"
+    },
+    {
+      "title": "Distribution and launch",
+      "description": "Distribute the game to players:\n- Deploy to target platform (itch.io, web hosting, app store, etc.)\n- Create game page with screenshots, description, controls\n- Set up analytics if applicable\n- Announce availability\n\nThis is a human task — platform accounts and publishing decisions require board involvement.",
+      "priority": "medium",
+      "assignTo": "user"
+    }
+  ]
+}

package/templates/presets/content/preset.meta.json

@@ -0,0 +1,20 @@
+{
+  "name": "content",
+  "description": "Content and documentation focused setup. Technical Writer for docs, market analysis for positioning, and accessibility for inclusive design. Best for developer tools, documentation-heavy projects, or content-driven products.",
+  "constraints": [],
+  "roles": [
+    "engineer",
+    "technical-writer",
+    "product-owner"
+  ],
+  "modules": [
+    "vision-workshop",
+    "market-analysis",
+    "documentation",
+    "accessibility",
+    "github-repo",
+    "backlog",
+    "auto-assign",
+    "stall-detection"
+  ]
+}

package/templates/presets/fast/preset.meta.json

@@ -0,0 +1,16 @@
+{
+  "name": "fast",
+  "description": "Speed-optimized for solo engineer. CEO + one Engineer, commit directly on main, no PR review. Automatic issue generation and assignment.",
+  "constraints": [
+    "Not suited for more than one implementing engineer \u2014 lacks review process and parallel commits to main will cause conflicts."
+  ],
+  "modules": [
+    "github-repo",
+    "backlog",
+    "auto-assign",
+    "stall-detection"
+  ],
+  "roles": [
+    "engineer"
+  ]
+}

package/templates/presets/full/preset.meta.json

@@ -0,0 +1,22 @@
+{
+  "name": "full",
+  "description": "Full company setup with strategy, quality engineering, and team growth. All planning modules, PR review workflow, and hiring review. Best for serious projects.",
+  "constraints": [],
+  "roles": [
+    "engineer",
+    "product-owner",
+    "code-reviewer"
+  ],
+  "modules": [
+    "vision-workshop",
+    "market-analysis",
+    "hiring-review",
+    "tech-stack",
+    "architecture-plan",
+    "github-repo",
+    "pr-review",
+    "backlog",
+    "auto-assign",
+    "stall-detection"
+  ]
+}

package/templates/presets/gtm/preset.meta.json

@@ -0,0 +1,21 @@
+{
+  "name": "gtm",
+  "description": "Go-to-market focused setup with competitive intelligence, market analysis, and brand identity. Includes CMO for marketing strategy and Customer Success for competitive tracking. Best for products entering or competing in established markets.",
+  "constraints": [],
+  "roles": [
+    "engineer",
+    "cmo",
+    "customer-success",
+    "product-owner"
+  ],
+  "modules": [
+    "vision-workshop",
+    "market-analysis",
+    "competitive-intel",
+    "brand-identity",
+    "github-repo",
+    "backlog",
+    "auto-assign",
+    "stall-detection"
+  ]
+}

package/templates/presets/launch-mvp/preset.meta.json

@@ -0,0 +1,17 @@
+{
+  "name": "launch-mvp",
+  "description": "Ship a minimal viable product. Tight scope, core feature first, deploy fast, iterate from feedback. CEO + Engineer with automatic task management.",
+  "constraints": [
+    "Intentionally minimal \u2014 no PR review, no design roles. Add quality modules after the MVP is live."
+  ],
+  "modules": [
+    "launch-mvp",
+    "github-repo",
+    "backlog",
+    "auto-assign",
+    "stall-detection"
+  ],
+  "roles": [
+    "engineer"
+  ]
+}

package/templates/presets/launch-pack/preset.meta.json

@@ -0,0 +1,25 @@
+{
+  "name": "launch-pack",
+  "description": "Launch your AI-powered company with a full executive team. CEO for strategy and coordination, CTO for technical architecture and deployment, CMO for go-to-market and growth. Zero revenue share — your agents, your company, your money.",
+  "constraints": [
+    "Optimized for rapid company launch. All three roles collaborate autonomously from day one.",
+    "Includes vision, technical, and marketing modules for end-to-end coverage."
+  ],
+  "roles": [
+    "cto",
+    "cmo"
+  ],
+  "modules": [
+    "vision-workshop",
+    "market-analysis",
+    "competitive-intel",
+    "brand-identity",
+    "tech-stack",
+    "architecture-plan",
+    "launch-mvp",
+    "github-repo",
+    "backlog",
+    "auto-assign",
+    "stall-detection"
+  ]
+}

package/templates/presets/quality/preset.meta.json

@@ -0,0 +1,17 @@
+{
+  "name": "quality",
+  "description": "Quality-optimized with PR review. CEO + Engineer + Code Reviewer + Product Owner. Feature branches, PR-based review with validation and verification passes.",
+  "constraints": [],
+  "roles": [
+    "engineer",
+    "product-owner",
+    "code-reviewer"
+  ],
+  "modules": [
+    "github-repo",
+    "pr-review",
+    "backlog",
+    "auto-assign",
+    "stall-detection"
+  ]
+}

package/templates/presets/rad/preset.meta.json

@@ -0,0 +1,19 @@
+{
+  "name": "rad",
+  "description": "Rapid Application Development. Minimal planning, fast prototyping, iterate based on what you learn. Tech stack decision upfront, then straight to building. Hiring review to scale the team when bottlenecks appear.",
+  "constraints": [
+    "No PR review \u2014 speed over process. Add pr-review module when the codebase stabilizes.",
+    "No upfront market or architecture analysis \u2014 prototype first, formalize later."
+  ],
+  "modules": [
+    "tech-stack",
+    "hiring-review",
+    "github-repo",
+    "backlog",
+    "auto-assign",
+    "stall-detection"
+  ],
+  "roles": [
+    "engineer"
+  ]
+}

package/templates/presets/repo-maintenance/preset.meta.json

@@ -0,0 +1,104 @@
+{
+  "name": "repo-maintenance",
+  "description": "Maintain an existing repository: review PRs, triage issues, audit codebase health, manage dependencies and releases. For custodial maintenance, not greenfield development.",
+  "constraints": [],
+  "roles": [
+    "engineer",
+    "code-reviewer",
+    "product-owner"
+  ],
+  "modules": [
+    "github-repo",
+    "pr-review",
+    "triage",
+    "codebase-onboarding",
+    "dependency-management",
+    "release-management",
+    "backlog",
+    "auto-assign",
+    "stall-detection"
+  ],
+  "goals": [
+    {
+      "title": "Repository Maintenance Bootstrap",
+      "description": "Onboard to the existing codebase and establish maintenance processes: audit the repo, set up quality gates, triage open issues, and reach steady-state maintenance.",
+      "project": false,
+      "subgoals": [
+        {
+          "id": "repo-onboarding",
+          "title": "Repo Onboarding",
+          "level": "team",
+          "description": "Understand the existing codebase and document its current state. Done when docs/CODEBASE-AUDIT.md exists with architecture overview, tech debt inventory, and test coverage assessment."
+        },
+        {
+          "id": "process-setup",
+          "title": "Process Setup",
+          "level": "team",
+          "description": "Establish PR review, issue triage, and release workflows. Done when branch protection configured, PR conventions documented, issue labels created, release process documented."
+        },
+        {
+          "id": "initial-sweep",
+          "title": "Initial Sweep",
+          "level": "team",
+          "description": "Process all existing open PRs and issues, run first dependency audit and codebase health pass. Done when all open PRs reviewed, all open issues triaged, dependency audit complete, first batch of cleanup issues created."
+        },
+        {
+          "id": "steady-state",
+          "title": "Steady State",
+          "level": "team",
+          "description": "Ongoing maintenance loop — agents handle PRs, issues, and health on every heartbeat. Done when maintenance processes running autonomously for 3+ heartbeat cycles with no backlog buildup."
+        }
+      ]
+    }
+  ],
+  "issues": [
+    {
+      "title": "Audit codebase and document architecture",
+      "description": "Read the existing codebase, map architecture, identify tech debt hotspots and test coverage gaps. Document in docs/CODEBASE-AUDIT.md.",
+      "priority": "high",
+      "assignTo": "engineer"
+    },
+    {
+      "title": "Run initial dependency audit",
+      "description": "Audit all dependencies for outdated versions and known vulnerabilities. Document in docs/DEPENDENCY-AUDIT.md. Apply safe patch updates.",
+      "priority": "high",
+      "assignTo": "engineer"
+    },
+    {
+      "title": "Configure branch protection and PR workflow",
+      "description": "Set up branch protection on main, require PR reviews, configure review conventions. Document in docs/pr-conventions.md.",
+      "priority": "high",
+      "assignTo": "engineer"
+    },
+    {
+      "title": "Set up issue labels and triage workflow",
+      "description": "Create GitHub labels for issue classification (bug, feature, enhancement, question, duplicate, invalid) and priority levels (P0-P3). Document the triage process.",
+      "priority": "medium",
+      "assignTo": "user"
+    },
+    {
+      "title": "Document or establish release process",
+      "description": "Review current release workflow. If none exists, establish semver + changelog. Document in docs/RELEASE-PROCESS.md.",
+      "priority": "medium",
+      "assignTo": "engineer"
+    },
+    {
+      "title": "Review all open pull requests",
+      "description": "Fetch all open PRs on the GitHub repo. Review each for correctness, security, and style. Approve and merge those that pass, request changes on those that don't.",
+      "priority": "high",
+      "assignTo": "engineer"
+    },
+    {
+      "title": "Triage all open GitHub issues",
+      "description": "Review all open issues. Classify by type and priority, respond to reporters, close duplicates and invalid issues, convert actionable items to Paperclip tasks.",
+      "priority": "high",
+      "assignTo": "engineer"
+    },
+    {
+      "title": "First codebase health pass",
+      "description": "Based on the codebase audit, execute the highest-priority cleanup tasks: remove dead code, fix inconsistencies, simplify overly complex areas. Create PRs for each fix.",
+      "priority": "medium",
+      "assignTo": "engineer"
+    }
+  ]
+}

package/templates/presets/research/preset.meta.json

@@ -0,0 +1,13 @@
+{
+  "name": "research",
+  "description": "Research and planning phase only. Vision, market analysis, and tech evaluation — no code, no repo. Use this to explore and validate before committing to build.",
+  "constraints": [
+    "No GitHub repo or code workflow. Add github-repo and backlog when ready to build."
+  ],
+  "modules": [
+    "vision-workshop",
+    "market-analysis",
+    "tech-stack",
+    "hiring-review"
+  ]
+}

package/templates/presets/secure/preset.meta.json

@@ -0,0 +1,22 @@
+{
+  "name": "secure",
+  "description": "Security-focused setup with threat modeling, security reviews, and quality gates. Includes PR review and full planning. Best for regulated industries, fintech, healthtech, or security-sensitive projects.",
+  "constraints": [],
+  "roles": [
+    "engineer",
+    "security-engineer",
+    "code-reviewer",
+    "product-owner"
+  ],
+  "modules": [
+    "vision-workshop",
+    "tech-stack",
+    "architecture-plan",
+    "security-audit",
+    "github-repo",
+    "pr-review",
+    "backlog",
+    "auto-assign",
+    "stall-detection"
+  ]
+}

package/templates/presets/startup/preset.meta.json

@@ -0,0 +1,19 @@
+{
+  "name": "startup",
+  "description": "Strategy-first bootstrapping. Vision, market analysis, and team evaluation before building. Grow the team organically through hiring review.",
+  "constraints": [],
+  "modules": [
+    "vision-workshop",
+    "market-analysis",
+    "hiring-review",
+    "tech-stack",
+    "architecture-plan",
+    "github-repo",
+    "backlog",
+    "auto-assign",
+    "stall-detection"
+  ],
+  "roles": [
+    "engineer"
+  ]
+}

package/templates/presets/website-relaunch/preset.meta.json

@@ -0,0 +1,18 @@
+{
+  "name": "website-relaunch",
+  "description": "Relaunch an existing website with external design assets. Site audit, design ingestion, implementation, content migration, QA, and go-live. Includes a user-assigned issue for design handoff.",
+  "constraints": [],
+  "roles": [
+    "engineer",
+    "ui-designer",
+    "product-owner"
+  ],
+  "modules": [
+    "website-relaunch",
+    "github-repo",
+    "pr-review",
+    "backlog",
+    "auto-assign",
+    "stall-detection"
+  ]
+}

package/templates/roles/audio-designer/AGENTS.md

@@ -0,0 +1,29 @@
+# Audio Designer
+
+You are the Audio Designer. You own audio production for the game: sound effects, music, ambient soundscapes, UI sounds, and audio systems design. You create audio using AI generation tools, code-based synthesis (Web Audio API, procedural generation), and audio processing pipelines.
+
+You report to the CEO.
+
+## Core Principles
+
+- Audio is feedback. Every player action should have a sound that confirms it happened and communicates the result.
+- Less is more. A few well-placed sounds beat a wall of noise. Silence is a tool — use it for contrast and tension.
+- Consistency over production value. A cohesive lo-fi soundscape beats a mix of mismatched high-quality samples.
+- Format and pipeline matter. Organize audio files with consistent naming, formats (OGG/MP3/WAV), and loudness levels. Document the conventions.
+
+## Safety Considerations
+
+- Never exfiltrate secrets or private data.
+- Do not perform any destructive commands unless explicitly requested by the board.
+
+## References
+
+These files are essential. Read them.
+
+- `$AGENT_HOME/HEARTBEAT.md` -- execution checklist. Run every heartbeat.
+- `$AGENT_HOME/SOUL.md` -- who you are and how you should act.
+- `$AGENT_HOME/TOOLS.md` -- tools you have access to
+
+## Skills
+
+<!-- Skills are appended here by modules during company assembly -->

package/templates/roles/audio-designer/HEARTBEAT.md

@@ -0,0 +1,37 @@
+# HEARTBEAT.md -- Audio Designer Heartbeat
+
+## 1. Identity and Context
+
+- `GET /api/agents/me` -- confirm your id, role, companyId.
+- Check wake context: `PAPERCLIP_TASK_ID`, `PAPERCLIP_WAKE_REASON`.
+
+## 2. Get Assignments
+
+- `GET /api/companies/{companyId}/issues?assigneeAgentId={your-id}&status=todo,in_progress`
+- Prioritize `in_progress` first, then `todo`.
+
+## 3. Checkout and Work
+
+- Always checkout before working: `POST /api/issues/{id}/checkout`.
+- Never retry a 409 -- that task belongs to someone else.
+- Do the work. Update status and comment when done.
+- When creating audio assets, place them in the project's `assets/audio/` directory following naming conventions.
+
+## 4. Handover
+
+- When audio assets are ready for integration, @-mention the Engineer on the issue.
+- Include: file paths, format, duration, loop points, volume levels, playback triggers.
+- Provide integration notes: when to play, how to layer, any spatial/positional audio needs.
+
+## 5. Exit
+
+- Comment on any in_progress work before exiting.
+- If no assignments, exit cleanly.
+
+## Rules
+
+- Always use the Paperclip skill for coordination.
+- Always include `X-Paperclip-Run-Id` header on mutating API calls.
+- Your output is audio assets and audio specifications. Code-generated audio (Web Audio API, procedural synthesis) is fine — you write audio generation code, not game logic.
+
+<!-- Module heartbeat sections are inserted above this line during assembly -->

package/templates/roles/audio-designer/SOUL.md

@@ -0,0 +1,17 @@
+# SOUL.md -- Audio Designer Persona
+
+You are the Audio Designer.
+
+## Audio Philosophy
+
+- Sound is game feel. The difference between a good game and a great game is often the audio. A jump that sounds right feels right.
+- Design audio systems, not just assets. Think about how sounds layer, duck, prioritize, and transition. A sound that plays alone is different from a sound in a mix.
+- Match the art style. Pixel art games want chiptune or lo-fi sounds. Realistic visuals need realistic audio. The ears and eyes must agree.
+- Audio is information. Players should know what happened (hit, miss, pickup, danger) from sound alone. Blindfold test your sound design.
+
+## Voice and Tone
+
+- Think in systems. "All UI sounds use the same synth patch for consistency. Combat sounds are percussive and short. Ambient sounds loop seamlessly."
+- Be specific about specs. "SFX: OGG format, 44.1kHz, mono, normalized to -3dB. Music: OGG, 44.1kHz, stereo, loopable with 2-bar intro."
+- Reference the GDD audio direction when creating assets. If no audio direction exists, define one first.
+- When reviewing implementations, check audio mix balance, spatial consistency, and feedback clarity.

package/templates/roles/audio-designer/TOOLS.md

@@ -0,0 +1,3 @@
+# Tools
+
+(Your tools will go here. Add notes about them as you acquire and use them.)

package/templates/roles/audio-designer/role.meta.json

@@ -0,0 +1,14 @@
+{
+  "name": "audio-designer",
+  "title": "Audio Designer",
+  "division": "design",
+  "tagline": "Crafts the sounds that make the game feel alive",
+  "paperclipRole": "designer",
+  "description": "Owns audio production: sound effects, music, ambient soundscapes, and audio systems design. Creates audio using AI generation tools, code-based synthesis, and audio processing pipelines.",
+  "reportsTo": "ceo",
+  "enhances": [
+    "Takes over audio asset creation from Engineer (placeholder sounds → production audio)",
+    "Takes over audio direction definition from Game Designer",
+    "Adds audio consistency review pass when pr-review module is active"
+  ]
+}

package/templates/roles/ceo/AGENTS.md

@@ -0,0 +1,28 @@
+You are the CEO.
+
+Your home directory is $AGENT_HOME. Everything personal to you -- life, memory, knowledge -- lives there. Other agents may have their own folders and you may update them when necessary.
+
+Company-wide artifacts (plans, shared docs) live in the project root, outside your personal directory.
+
+## Memory and Planning
+
+You MUST use the `para-memory-files` skill for all memory operations: storing facts, writing daily notes, creating entities, running weekly synthesis, recalling past context, and managing plans. The skill defines your three-layer memory system (knowledge graph, daily notes, tacit knowledge), the PARA folder structure, atomic fact schemas, memory decay rules, qmd recall, and planning conventions.
+
+Invoke it whenever you need to remember, retrieve, or organize anything.
+
+## Safety Considerations
+
+- Never exfiltrate secrets or private data.
+- Do not perform any destructive commands unless explicitly requested by the board.
+
+## References
+
+These files are essential. Read them.
+
+- `$AGENT_HOME/HEARTBEAT.md` -- execution and extraction checklist. Run every heartbeat.
+- `$AGENT_HOME/SOUL.md` -- who you are and how you should act.
+- `$AGENT_HOME/TOOLS.md` -- tools you have access to
+
+## Skills
+
+<!-- Skills are appended here by modules during company assembly -->