Pending: Scope of autonomous implementation (which feature types can be auto-built)
User Tasks
Summary
Enable Opus to autonomously implement new features, run tests, and improve itself.
Problem / Motivation
Currently every change requires a human-initiated Claude Code session. The system
should be able to pick up planned features and implement them with minimal oversight.
Proposed Solution
Autonomous build loop: pick a planned feature, implement, test, mark done.
Human reviews and approves before deployment.
This is a long-term vision feature. Many prerequisites needed first (VPS, testing, automation).
Open Questions
⇒
No open questions.
Phase Overview
Phase
Description
Status
Phase 1
Foundations
—
Phase 2
Autonomous Implementation
—
Phase 3
Business Ideas
—
Phase 1: Foundations —
Goal: Build the testing and analysis infrastructure needed for autonomous work.
File / Feature
Details
Owner
Status
Unit tests
Unit tests for all features (testable acceptance criteria)
mv
—
Capability list
A list of everything the system should be able to do
opus
—
Feature analysis
Regular feature and technical analysis
opus
—
Phase 2: Autonomous Implementation —
Goal: Enable Opus to pick up and implement planned features autonomously.
File / Feature
Details
Owner
Status
Feature pickup
Agent picks up planned feature requests
opus
—
Implement from spec
Implements according to spec
opus
—
Auto-test
Runs tests automatically
mv
—
Create PR
Creates PR for human review
mv
—
Phase 3: Business Ideas —
Goal: Use autonomous capabilities to explore digital product ideas.
File / Feature
Details
Owner
Status
Idea generation
Generate and evaluate digital product ideas
mv
—
Prototype
Prototype autonomously
opus
—
Report results
Report results to user
mv
—
Prerequisites / Gap Analysis
Requirements
Requirement
Description
REQ-1
System can implement a simple feature request without human coding
REQ-2
All changes pass automated tests before being proposed
Current State
Component
Status
Details
Testing infrastructure
—
No automated tests exist
VPS
—
FR-019 not yet started
CI/CD
—
No pipeline exists
Gap (What’s missing?)
Gap
Effort
Blocker?
Testing infrastructure
High
Yes
VPS deployment (FR-019)
High
Yes
CI/CD pipeline
Med
Yes
Test
Manual tests
Test
Expected
Actual
Last
Human review gate
Changes not deployed without approval
pending
-
AI-verified tests
Scenario
Expected behavior
Verification method
…
…
…
E2E tests
Scenario
Assertion
…
…
Integration tests
Component
Coverage
…
…
Unit tests
Component
Tests
Coverage
…
…
…
History
Date
Event
Details
2026-02-26
Created
Created from brain dump
2026-02-27
Renumbered
From FR-015 to FR-066
2026-02-28
Rewritten
Aligned to feature-request template
References
FR-019 (VPS Deployment) — needed for always-on autonomous execution
FR-010 (GitHub Integration) — needed for PR creation
vault/00_system/logs/self-improvement-log.md — activate when this FR goes live (currently deferred, git history used as audit trail)