Metagenda

Metagenda helps a small team deliver more work across projects without a corresponding increase in coordination overhead. It brings together idea refinement, priorities, work sessions, progress tracking, reviews, retrospectives, and resource allocation.

AI supports this work through a custom Pi harness, locally owned extensions, and a pipeline for research, implementation, independent checks, and reporting. Telegram provides a conversational interface. GitHub issues, sub-issues, and roadmap PRs connect plans to delivery; human time and AI usage are managed against project priorities.

Adjustable resource allocations and dynamic throttling keep background work within usage limits while preserving responsive interactive sessions.

The portable fj package provides repository and tracker inspection. The broader Telegram planning and orchestration workflow remains in development.

Documentation

• SPEC.md: product direction and capability contracts.
• ROADMAP.md: prioritized outcomes and delivery work.
• AGENTS.md: engineering workflow and operating rules.

Packages

• tooling/fj/: portable repository status and GitHub issue/PR list/view. It has no mutation or host/session management commands; explicit view --web may open a browser through gh.
• packages/work-core/: private ESM package for canonical-backlog decoding and normalization, with compiled exports and consumer checks.
• pi/skills.nix: packages public Pi skill documents and support files with pinned source hashes and preserved MIT attribution. The skills provenance record documents the source and package layout. Installing skill documents does not activate extensions or services.

See the roadmap for shared runtime and service integration.

Portable fj

nix run .#fj -- help runs the fj app. nix build .#fj builds the package, including isolated Nu tests. The package exposes bin/fj and share/nushell/fj/mod.nu with sibling modules. For local tests, use bun run test:fj with Nu from the development shell.

Commands are default repository status, help, issue list, issue view, pr list, and pr view. List forwards gh flags; view supports --comments and explicit browser-opening --web. Omitted PR IDs use the caller's current branch. Repository context never changes to the installation directory.

But is optional on PATH and is used only for default status in a main worktree with the gitbutler/* branch heuristic. Missing or failing But is an error there; linked and unmanaged worktrees use Git. This heuristic grants no authority.

Source provenance and compatibility contracts document the package source and integration boundaries.

Development

flake.nix declares the toolchain, including Node 26 and GitButler from the pinned dataclique/but.nix input. Use but in the main checkout and plain Git in linked worktrees. Bun manages JavaScript dependencies through bun.lock; bun.nix supplies Nix builds.

From a configured development shell:

bun install --frozen-lockfile --ignore-scripts
bun run typecheck
bun run test
bun run build

bun run test:job-attempt checks attempt-event validation, ordering, duplicate receipts, and terminal transitions. bun run typecheck:job-attempt checks its TypeScript contract. Both run through verify; neither starts workers or tests persistence.

After dependency changes, regenerate bun.nix with the pinned bun2nix tool before building with Nix:

bun2nix --lock-file bun.lock --output-file bun.nix

bun run lint checks active workspaces without changing files; bun run lint:fix applies fixes explicitly. The aggregate verify script runs typechecking, linting, tests, and builds. These commands describe verification steps; they do not claim that all checks pass.