@davehardy20/pi-seeds

Pi package for per-project issue management via the Seeds CLI (sd).

What it adds

Tools (15)

| Tool | Description | | --- | --- | | seeds_prime | Fetch Seeds workflow context (sd prime) | | seeds_list | List / ready / blocked / stats | | seeds_show | Show one issue in detail | | seeds_doctor | Project health checks | | seeds_create | Create a new issue | | seeds_update | Update an existing issue | | seeds_close | Close one or more issues | | seeds_relation | Manage dependencies and blockers | | seeds_project | Project-level actions (init, sync, onboard) | | seeds_plan_prompt | Generate a structured planning prompt | | seeds_plan_show | Inspect a submitted plan and child seeds | | seeds_plan_validate | Re-validate stored plan structure | | seeds_plan_submit | Submit a filled plan JSON document | | seeds_plan_review | Record reviewer metadata on a plan | | seeds_plan_outcome | Record plan outcome and optional Mulch decision |

Commands (3)

| Command | Description | | --- | --- | | /seeds <subcommand> | Seeds issue tracker commands (status, ready, blocked, show, prime, doctor, create, update, close, init, sync, onboard) | | /seeds-plan <subcommand> | Seeds plan workflow commands (prompt, show, validate, review, outcome) | | /seeds-status | Show package version and CLI availability |

Seeds CLI requirement

This package requires the Seeds CLI (sd) to be available. It tries these runners in order:

1. sd (direct binary)
2. bunx --package @os-eco/seeds-cli sd
3. npx --yes @os-eco/seeds-cli

Install

From npm:

pi install npm:@davehardy20/pi-seeds

From git:

pi install git:github.com/davehardy20/pi-seeds

From a local checkout during development:

pi install /Users/dave/tools/pi-seeds

For one run only:

pi -e /Users/dave/tools/pi-seeds

Settings

No special Pi settings are required. The extension works in any project directory that has a .seeds/ directory (or where you want to initialize one with sd init).

The Seeds CLI must be available in the system PATH or via bunx/npx.

Update flow

1. Update the package repo
2. Push to GitHub
3. Run pi update --extensions or reinstall the package
4. Run /reload

/reload alone does not fetch newer package commits.

Troubleshooting

Run /seeds-status to confirm:

• Package name and version
• Loaded source path
• Seeds CLI availability and runner

If commands appear twice, Pi may be loading both the package and the old local extension. Disable or remove the old local auto-discovered extension before reload verification.

If the Seeds CLI is not found, install it globally or ensure bun/npm is available in your PATH.

Build and test

npm run typecheck
npm run build
npm test