Self-learning engineering assistant for Kiro CLI. Structured methodology, persistent memory, continuous improvement.
PILOT extends Kiro CLI with:
- Universal Algorithm — Structured approach to every engineering task
- Self-learning — Captures verified solutions and applies them to future work
- Persistent memory — Three-tier system (hot/warm/cold) that grows with you
- Identity awareness — Knows your goals, projects, and strategies
- Working modes — Hands-on execution or advisory discussion
- Delegation — Routes specialized tasks to expert agents
PILOT follows the Universal Algorithm: Current State → Ideal State via verifiable iteration
Every task follows seven phases:
- OBSERVE — Understand current reality (never assume)
- THINK — Generate multiple approaches
- PLAN — Select strategy and sequence
- BUILD — Define success criteria BEFORE executing
- EXECUTE — Do the work (or delegate to specialists)
- VERIFY — Test against criteria objectively
- LEARN — Extract insights only after verification confirms success
Key principle: "Verifiability is everything" — Define what success looks like BEFORE you execute.
./install.shThe installer will:
- Create
~/.kiro/pilot/directory structure (system files) - Create
~/.pilot/directory (user data: learnings, identity) - Install the pilot agent to
~/.kiro/agents/ - Set up hook scripts for automation
- Copy identity templates and resources
./verify.sh- Open Kiro CLI
- Select the
pilotagent - Start working — PILOT follows the Algorithm automatically
PILOT uses two locations:
~/.pilot/ # User data (learnings, identity)
├── learnings/ # Captured solutions and insights
└── identity/ # Your personal context
~/.kiro/ # Kiro system files
├── pilot/ # PILOT system
│ ├── memory/ # Hot/Warm/Cold storage
│ │ ├── hot/ # Current session
│ │ ├── warm/ # Recent context
│ │ └── cold/ # Archive
│ ├── resources/ # Algorithm & Principles
│ └── metrics/ # Session metrics
├── agents/pilot.json # Agent configuration
├── hooks/pilot/ # Hook scripts
└── steering/pilot/ # Steering files
Important: Learnings are saved to ~/.pilot/learnings/, not ~/.kiro/pilot/.
PILOT can operate in two modes:
| Mode | Description | Use When |
|---|---|---|
| Hands-on | Directly edit files, run commands, implement | You want PILOT to do the work |
| Advisory | Discuss, plan, delegate execution | You want to discuss before acting |
Switch modes by telling PILOT: "Let's just discuss this" or "Go ahead and implement".
PILOT delegates to specialized agents when appropriate:
- Specialized expertise — Terraform, Kubernetes, specific frameworks
- Parallel work — Run multiple tasks simultaneously
- User preference — Keep PILOT in advisory mode
- Long-running operations — Don't block conversation
Delegation strategy:
- Find specialist agent matching the task domain
- Fall back to
kiro_defaultif no specialist found - Report results back to user
PILOT captures learnings from verified solutions:
- Fixed a bug and verified the fix works
- Discovered a pattern and tested it
- Found a solution and confirmed it solves the problem
- Proposed solution not yet verified
- Routine tasks without insights
- Simple lookups
Learnings are stored in ~/.pilot/learnings/ and searchable via the knowledge tool.
PILOT works without identity files, but becomes more personalized when configured.
Edit files in ~/.pilot/identity/:
| File | Purpose |
|---|---|
MISSION.md |
Your ultimate goal |
GOALS.md |
Specific objectives |
PROJECTS.md |
Current work |
BELIEFS.md |
Core convictions |
STRATEGIES.md |
Proven approaches |
LEARNED.md |
Past lessons |
CHALLENGES.md |
Current obstacles |
All implemented as bash hooks — no external dependencies.
| Feature | What It Does |
|---|---|
| Memory | Three-tier storage with automatic archiving |
| Self-Learning | Captures verified solutions for future reference |
| Security | Multi-tier command validation |
| Monitoring | Session metrics and tracking |
PILOT uses a modular pack system. See:
packs/pilot-core/— Core pack (installed by default)packs/pilot-pack-template/— Template for creating new packsPACK-DEVELOPMENT.md— Pack development guide
- Bash-only — No TypeScript, no external runtimes
- Single directory — System in
~/.kiro/, user data in~/.pilot/ - Hook-based — All features via Kiro's native hooks
- Fail-safe — Hooks always exit 0, never break Kiro
- Verified learning — Only capture learnings after verification
Inspired by Personal AI Infrastructure (PAI) by Daniel Miessler.
PILOT adapts PAI's modular architecture to Kiro CLI, focusing on engineering workflows with a bash-only implementation.
MIT License — Use freely, commercially or personally.