mirror of
https://github.com/PR0M3TH3AN/SeedPass.git
synced 2026-11-06 21:02:04 +00:00
thePR0M3TH3ANandClaude Opus 4.6
ca31abf33e
- Update agent models from gpt-5.3-codex to claude-compatible names (opus for coordinator/lead, sonnet for builder/scout/reviewer/merger, haiku for monitor) - Switch runtime from codex to claude (codex requires interactive TTY, incompatible with tmux-based agent spawning) - Add Overstory ecosystem links to AGENTS.md and CLAUDE.md - Add docs/overstory_quick_reference.md with startup, monitoring, and CLI commands - Sync seeds issue state Co-Authored-By: Claude Opus 4.6 <[email protected]>
117 lines
4.2 KiB
Markdown
117 lines
4.2 KiB
Markdown
# SeedPass Agent Guide
|
|
|
|
## Overstory Ecosystem
|
|
This project is part of the **Overstory** multi-agent development ecosystem. When asked to "update Overstory" or work on the ecosystem, these are the relevant repositories:
|
|
|
|
- **[Overstory](https://github.com/jayminwest/overstory)** — The coordinator. Orchestrates multi-agent workflows across worktrees.
|
|
- **[Mulch](https://github.com/jayminwest/mulch)** — Structured expertise/memory system for agents.
|
|
- **[Canopy](https://github.com/jayminwest/canopy)** — Prompt management system for agents.
|
|
- **[Seeds](https://github.com/jayminwest/seeds)** — Git-native issue tracker for agents.
|
|
- **[os-eco](https://github.com/jayminwest/os-eco)** — The entire Overstory ecosystem (meta-repo/docs).
|
|
|
|
## Planning & Strategy
|
|
Consult these first to align with current objectives:
|
|
- **[Dev Control Center](docs/dev_control_center.md)**: Current priorities.
|
|
- **[TUI v2 Execution Plan](docs/tui_v2_integration_execution_plan_2026-03-02.md)**: Roadmap for TUI v2.
|
|
|
|
## Testing
|
|
Always run the full suite before proposing changes:
|
|
- `bash scripts/run_ci_tests.sh`
|
|
- Central Index: **[Test Infrastructure Inventory](docs/TEST_INVENTORY.md)**
|
|
|
|
## TORCH Memory Integration
|
|
You have access to the TORCH memory system.
|
|
1. READ: Check `.scheduler-memory/latest/${cadence}/memories.md` for past learnings.
|
|
2. WRITE: Before exiting, save new insights to `memory-update.md` so future runs can learn from this session.
|
|
|
|
<!-- mulch:start -->
|
|
## Project Expertise (Mulch)
|
|
<!-- mulch-onboard-v:1 -->
|
|
|
|
This project uses [Mulch](https://github.com/jayminwest/mulch) for structured expertise management.
|
|
|
|
**At the start of every session**, run:
|
|
```bash
|
|
mulch prime
|
|
```
|
|
|
|
This injects project-specific conventions, patterns, decisions, and other learnings into your context.
|
|
Use `mulch prime --files src/foo.ts` to load only records relevant to specific files.
|
|
|
|
**Before completing your task**, review your work for insights worth preserving — conventions discovered,
|
|
patterns applied, failures encountered, or decisions made — and record them:
|
|
```bash
|
|
mulch record <domain> --type <convention|pattern|failure|decision|reference|guide> --description "..."
|
|
```
|
|
|
|
Link evidence when available: `--evidence-commit <sha>`, `--evidence-bead <id>`
|
|
|
|
Run `mulch status` to check domain health and entry counts.
|
|
Run `mulch --help` for full usage.
|
|
Mulch write commands use file locking and atomic writes — multiple agents can safely record to the same domain concurrently.
|
|
|
|
### Before You Finish
|
|
|
|
1. Discover what to record:
|
|
```bash
|
|
mulch learn
|
|
```
|
|
2. Store insights from this work session:
|
|
```bash
|
|
mulch record <domain> --type <convention|pattern|failure|decision|reference|guide> --description "..."
|
|
```
|
|
3. Validate and commit:
|
|
```bash
|
|
mulch sync
|
|
```
|
|
<!-- mulch:end -->
|
|
|
|
<!-- seeds:start -->
|
|
## Issue Tracking (Seeds)
|
|
<!-- seeds-onboard-v:1 -->
|
|
|
|
This project uses [Seeds](https://github.com/jayminwest/seeds) for git-native issue tracking.
|
|
|
|
**At the start of every session**, run:
|
|
```
|
|
sd prime
|
|
```
|
|
|
|
This injects session context: rules, command reference, and workflows.
|
|
|
|
**Quick reference:**
|
|
- `sd ready` — Find unblocked work
|
|
- `sd create --title "..." --type task --priority 2` — Create issue
|
|
- `sd update <id> --status in_progress` — Claim work
|
|
- `sd close <id>` — Complete work
|
|
- `sd sync` — Sync with git (run before pushing)
|
|
|
|
### Before You Finish
|
|
1. Close completed issues: `sd close <id>`
|
|
2. File issues for remaining work: `sd create --title "..."`
|
|
3. Sync and push: `sd sync && git push`
|
|
<!-- seeds:end -->
|
|
|
|
<!-- canopy:start -->
|
|
## Prompt Management (Canopy)
|
|
<!-- canopy-onboard-v:1 -->
|
|
|
|
This project uses [Canopy](https://github.com/jayminwest/canopy) for git-native prompt management.
|
|
|
|
**At the start of every session**, run:
|
|
```
|
|
cn prime
|
|
```
|
|
|
|
This injects prompt workflow context: commands, conventions, and common workflows.
|
|
|
|
**Quick reference:**
|
|
- `cn list` — List all prompts
|
|
- `cn render <name>` — View rendered prompt (resolves inheritance)
|
|
- `cn emit --all` — Render prompts to files
|
|
- `cn update <name>` — Update a prompt (creates new version)
|
|
- `cn sync` — Stage and commit .canopy/ changes
|
|
|
|
**Do not manually edit emitted files.** Use `cn update` to modify prompts, then `cn emit` to regenerate.
|
|
<!-- canopy:end -->
|