Quality Gate: 71-pillar | ARS: C (bootstrapping) | Tier-1 CI: 🔴 in progress
Project management system with AI agent integration — 24-crate Rust monorepo with hexagonal architecture, Python MCP server, and Plane.so/GitHub integration.
AgilePlus is a full-stack project management platform built with:
- Rust (24 crates) — Core domain, storage, event sourcing, CLI, REST API
- Python — MCP server for AI agent integration
- TypeScript — pheno-cli, React components
- Domain model: Feature, WorkPackage, Cycle, Module with state machines
- Event sourcing with audit trails and hash chains
- SQLite storage with hexagonal adapter pattern
- gRPC protocol definitions
- REST API with API key authentication
- OpenTelemetry tracing and metrics
- Git VCS adapter integration
- Plane.so sync (push/pull)
- GitHub integration
# Setup
cd AgilePlus
bun install
cargo build --workspace
# Run CLI
cargo run --package pheno-cli -- --help
# Start REST server
cargo run --package pheno-cli -- serve
# Run tests
cargo test --workspace| Document | Purpose |
|---|---|
| PLAN.md | Implementation phases and task tracking |
| PRD.md | Product requirements and user journeys |
| FUNCTIONAL_REQUIREMENTS.md | Detailed FR traceability |
| AGENTS.md | Agent interaction rules |
| GOVERNANCE.md | Project governance |
AgilePlus/
├── crates/ # 24 Rust crates (workspace)
├── python/ # Python MCP server
├── pheno-cli/ # CLI tool
├── kitty-specs/ # Feature specifications
├── docs/ # Documentation
└── harnesses/ # Agent harness configs
- Identify the project — Check
projects/INDEX.mdor ask the user - Navigate to project —
cd <project-name> - Read project rules — Check for
CLAUDE.mdorAGENTS.mdin project - Do the work — Follow shelf rules in
AGENTS.md - Commit & push — Use conventional commits, open PR if needed
This shelf contains many projects, of which AgilePlus is one.
AgilePlus-specific documentation lives inside the AgilePlus/ project directory,
not at shelf level.
The files that were previously here describing AgilePlus have been moved to their correct locations:
- AgilePlus governance →
AgilePlus/GOVERNANCE.md - AgilePlus agent rules →
AgilePlus/AGENTS.md - AgilePlus README →
AgilePlus/README.md
- Shelf-level issues: Ask here
- Project-specific issues:
cd <project>and check that project's docs - Architecture decisions:
cat docs/adr/INDEX.md - General questions: Check
projects/INDEX.mdfirst
This repo's WORKLOG.md uses the AgilePlus team-sprint schema (L#-# req_ids, device/topic/branch/scope/owner/eta + per-sprint entries). It coexists with the pheno-worklog-schema v2.0/v2.1 (L5-### req_ids, 10/11 columns) used by the fleet-substrate layer.
Per ADR-032, both schemas stay — they track different metadata (team-sprint vs. fleet-level), have non-colliding req_id prefixes, and the cost of forcing convergence is higher than the cost of divergence. The req_id is the join key if cross-schema audit is ever needed.
To query across both schemas, use the req_id prefix as a discriminator: L#-# (this repo) vs. L5-### (fleet substrate).