🤖 Make POW! agent-ready for autonomous AI development

[jeanclaw2026]

Strategic Context

Three POW! users reached out in a single day (Feb 25, 2026) when the server had a brief outage. That's real signal — people depend on this and miss it when it's gone.

POW! fits into a broader strategy of AI-assisted product revival — using autonomous agents to maintain and evolve side projects with minimal human involvement. The pattern established here will be reused for Pruner Follows and other projects.

The Vision

Queen Raae architects, AI agents execute. Low time investment, real products in the world. "I use AI to run multiple products with minimal overhead" becomes both the reality and the conference talk.

---

Phase 1: Make the repo agent-ready

Before any agent can work autonomously, the repo needs:

• AGENTS.md — Project bible: what is POW!, what's the stack, boundaries, how to run/test/deploy, what NOT to touch
• Working local dev setup — npm install && npm run dev must just work. Document any env vars, API keys, services needed
• CI/tests — Even minimal smoke tests. Agent needs a way to verify it didn't break things
• PR-based workflow — Branch protection on main. Agent always works via PRs for human review gate
• README refresh — Current state, architecture overview, deployment setup

Phase 2: Migrate off Gatsby

POW! is currently on a very old version of Gatsby. Two options were considered:

Option A: Stay on Gatsby, fix what's needed

• ✅ Lower risk, faster to agent-ready
• ❌ Building on a dying framework, diminishing returns

Option B (recommended): Migrate to modern stack (Astro, Next, or plain React)

• ✅ Agent can iterate long-term
• ✅ Migration is well-scoped, testable, mechanical — perfect first agent task
• ✅ Proves the autonomous agent pattern before applying to other projects
• ❌ Higher upfront cost

Recommendation: Make the migration itself the first autonomous agent project. It's well-scoped and testable (does the app still work?).

Migration checklist (once agent-ready):

• Audit current Gatsby site: pages, components, data sources, plugins
• Choose target framework
• Migrate page by page with parity checks
• Verify all functionality works
• Deploy to staging for manual review
• Cut over

Phase 3: Dedicated OpenClaw agent

Once the repo is agent-ready and migrated:

• Add a pow agent in OpenClaw config with its own workspace
• GitHub App access for creating PRs
• Error monitoring → agent gets notified → creates fix PRs
• Human review loop: Queen reviews PRs on phone, approve/reject, done
• Optional: cron-based health checks and proactive maintenance

Phase 4: Growth (future)

With autonomous maintenance solved, explore:

• Feature development via agent (user feedback → issue → agent PR)
• A/B testing and analytics
• Content updates and SEO improvements

---

Created by Jean-Claw 🦀 — to be picked up Wednesday March 4, 2026
Context: Strategy session Feb 26, 2026 (Telegram)