81 lines
2.6 KiB
Markdown
81 lines
2.6 KiB
Markdown
# Roadmap: ngn-agent
|
|
|
|
**Current Phase:** None yet — start with Phase 1
|
|
**Total Phases:** 4
|
|
**v1 Requirements:** 22 mapped — all covered ✓
|
|
|
|
---
|
|
|
|
### Phase 1: Hermes Install & Provider Setup
|
|
|
|
**Goal:** Hermes Agent installed, Docker backend configured with security hardening, Bedrock + OpenRouter providers configured, limited AWS role mounted, dangerous command approval active.
|
|
|
|
**Mode:** mvp
|
|
|
|
**Requirements:** AUTH-01, AUTH-02, AUTH-03, AUTH-04, AUTH-05, CONT-01, CONT-02, CONT-03, CONT-04, CONT-05, CONT-06
|
|
|
|
**Success Criteria:**
|
|
1. Hermes CLI starts and responds to a chat
|
|
2. Bedrock provider authenticates via SSO and generates a response
|
|
3. OpenRouter fallback works when Bedrock is unavailable
|
|
4. Docker container runs terminal commands with hardened flags
|
|
5. `./.aws` limited role is mounted read-only and accessible inside container
|
|
6. Dangerous command approval triggers on destructive patterns
|
|
7. `hermes doctor` passes cleanly
|
|
|
|
---
|
|
|
|
### Phase 2: Memory, Git & Session Management
|
|
|
|
**Goal:** Hermes persistent memory operational, session search working, git worktree isolation enabled, infrastructure facts auto-saved.
|
|
|
|
**Requirements:** MEM-01, MEM-02, MEM-03, MEM-04
|
|
|
|
**Success Criteria:**
|
|
1. Agent saves a fact to MEMORY.md and it persists across sessions
|
|
2. Session search finds a past conversation by keyword
|
|
3. `hermes -w` creates an isolated git worktree on a feature branch
|
|
4. Agent auto-saves environment facts without being asked
|
|
|
|
---
|
|
|
|
### Phase 3: Telegram Gateway
|
|
|
|
**Goal:** Telegram gateway operational with pairing-based authorization, scheduled tasks working.
|
|
|
|
**Requirements:** GATE-01, GATE-02, GATE-03, GATE-04
|
|
|
|
**Success Criteria:**
|
|
1. Telegram bot responds to DMs via Hermes gateway
|
|
2. New users receive pairing codes and can be approved
|
|
3. Scheduled daily report command generates a summary
|
|
4. Gateway handles multiple concurrent sessions
|
|
|
|
---
|
|
|
|
### Phase 4: Skills & Integrations
|
|
|
|
**Goal:** Skills system operational, Jira/Confluence MCP integration, read-only infra diagnostic skills.
|
|
|
|
**Requirements:** SKIL-01, SKIL-02, SKIL-03
|
|
|
|
**Success Criteria:**
|
|
1. Skills Hub browsable and installable via slash commands
|
|
2. Custom platform-engineering skill loads correctly
|
|
3. Jira ticket query returns results via MCP
|
|
4. Confluence page fetcher returns documentation content
|
|
5. Read-only AWS diagnostic skill works without mutations
|
|
|
|
---
|
|
|
|
## Phase Dependency Graph
|
|
|
|
```
|
|
Phase 1 (Install & Providers)
|
|
└── Phase 2 (Memory & Git) — needs Hermes running
|
|
└── Phase 3 (Gateway) — needs stable agent
|
|
└── Phase 4 (Skills) — needs gateway for remote skill interaction
|
|
```
|
|
|
|
All phases are sequential. No parallelization.
|