Name: implement-phase
Author: zcancio

Prompt file imported from zcancio/aide (.claude/commands/implement-phase.md). Copyright stays with the author.

Implement the next phase from docs/program_management/aide_launch_plan.md.

Process

Read docs/program_management/aide_launch_plan.md and identify which phase to implement (the user will specify, or pick the earliest incomplete phase).
For each checkbox item in that phase:
- Check if it's already implemented in the codebase
- If not, implement it following the patterns in CLAUDE.md and docs/aide_data_access.md
- Mark it as done when complete
After implementing each item, verify:
- Code follows Hard Rules from CLAUDE.md
- SQL is in repos/ only, parameterized, uses user_conn()
- Pydantic models used for all request/response
- No Google dependencies introduced
- Security checklist items for this area are satisfied (check docs/aide_security_checklist.md)
Run tests after each logical group of changes.
At the end, write a build log to docs/program_management/build_log/PHASE_X_Y_<NAME>.md:
- Filename format: PHASE_0_1_INFRASTRUCTURE.md, PHASE_1_2_DATA_MODEL.md, etc.
- Include:
  - Summary: What was implemented
  - What Was Built: List of files created/modified with descriptions
  - Security Checklist Compliance: Which items were satisfied
  - File Structure: Tree of new/modified files
  - Verification: Lint, format, test results
  - Next Steps: What remains in the launch plan
  - Status: ✅ Phase X.Y Complete with date
Update the launch plan checkbox items to [x] for completed work.

Important context per phase

Phase 0 (Foundation): ✅ Complete. 0.1 Infrastructure (Railway, Neon, CI/CD). 0.2 Auth (magic links via Resend, JWT cookies, RLS).
Phase 1 (Core Product):
- 1.1 Kernel: Primitives, reducer, renderer, assembly. Existing code in engine/kernel/.
- 1.2 Data Model: Neon Postgres with RLS. Follow docs/infrastructure/aide_data_access.md patterns exactly.
- 1.3 L2/L3 Orchestrator: L2 (Haiku) compiles intent → primitives. L3 (Sonnet) synthesizes schemas, handles images.
- 1.4 Web Chat UI: Full-viewport preview + floating chat overlay. See docs/prds/aide_editor_prd.md.
- 1.5 Signal Ear: signal-cli-rest-api on Railway. Core differentiator — "update your page from a text."
- 1.6 Published Page Serving: R2 static hosting via Cloudflare CDN. /s/{slug} route.
- 1.7 Reliability: Validation catches bad primitives. Retry logic. Event log is source of truth.
Phase 2 (Rate Limiting + Engine): Turn counting per-user (50/week free), weekly reset. Host engine files on R2 for distribution.
Phase 3 (Payments): Stripe Checkout for $10/mo Pro. Webhook handlers must verify signatures. Idempotent.
Phase 4 (Landing & Launch): Landing page at toaide.com. Seed templates. Launch checklist (Sentry, ToS, robots.txt).
Phase 5 (Distribution): Post-launch. Claude.ai Project, Claude Code skill, MCP server, Cowork plugin.

Install implement-phase and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Implement the next phase from docs/program_management/aide_launch_plan.md. ## Process 1. Read docs/program_management/aide_launch_plan.md and identify which phase to implement (the user will specify, or pick the earliest incomplete phase). 2. For each checkbox item in that phase: - Check if it's already implemented in the codebase - If not, implement it following the patterns in CLAUDE.md and docs/aide_data_access.md - Mark it as done when complete 3. After implementing each item, verify: - Code follows Hard Rules from CLAUDE.md - SQL is in repos/ only, parameterized, uses user_conn() - Pydantic models used for all request/response - No Google dependencies introduced - Security checklist items for this area are satisfied (check docs/aide_security_checklist.md) 4. Run tests after each logical group of changes. 5. At the end, write a build log to `docs/program_management/build_log/PHASE_X_Y_<NAME>.md`: - Filename format: `PHASE_0_1_INFRASTRUCTURE.md`, `PHASE_1_2_DATA_MODEL.md`, etc. - Include: - **Summary**: What was implemented - **What Was Built**: List of files created/modified with descriptions - **Security Checklist Compliance**: Which items were satisfied - **File Structure**: Tree of new/modified files - **Verification**: Lint, format, test results - **Next Steps**: What remains in the launch plan - **Status**: `✅ Phase X.Y Complete` with date 6. Update the launch plan checkbox items to `[x]` for completed work. ## Important context per phase - **Phase 0 (Foundation):** ✅ Complete. 0.1 Infrastructure (Railway, Neon, CI/CD). 0.2 Auth (magic links via Resend, JWT cookies, RLS). - **Phase 1 (Core Product):** - 1.1 Kernel: Primitives, reducer, renderer, assembly. Existing code in `engine/kernel/`. - 1.2 Data Model: Neon Postgres with RLS. Follow `docs/infrastructure/aide_data_access.md` patterns exactly. - 1.3 L2/L3 Orchestrator: L2 (Haiku) compiles intent → primitives. L3 (Sonnet) synthesizes schemas, handles images. - 1.4 Web Chat UI: Full-viewport preview + floating chat overlay. See `docs/prds/aide_editor_prd.md`. - 1.5 Signal Ear: signal-cli-rest-api on Railway. Core differentiator — "update your page from a text." - 1.6 Published Page Serving: R2 static hosting via Cloudflare CDN. `/s/{slug}` route. - 1.7 Reliability: Validation catches bad primitives. Retry logic. Event log is source of truth. - **Phase 2 (Rate Limiting + Engine):** Turn counting per-user (50/week free), weekly reset. Host engine files on R2 for distribution. - **Phase 3 (Payments):** Stripe Checkout for $10/mo Pro. Webhook handlers must verify signatures. Idempotent. - **Phase 4 (Landing & Launch):** Landing page at toaide.com. Seed templates. Launch checklist (Sentry, ToS, robots.txt). - **Phase 5 (Distribution):** Post-launch. Claude.ai Project, Claude Code skill, MCP server, Cowork plugin.

{ "prompt": "Implement the next phase from docs/program_management/aide_launch_plan.md.\n\n## Process\n\n1. Read docs/program_management/aide_launch_plan.md and identify which phase to implement (the user will specify, or pick the earliest incomplete phase).\n\n2. For each checkbox item in that phase:\n - Check if it's already implemented in the codebase\n - If not, implement it following the patterns in CLAUDE.md and docs/aide_data_access.md\n - Mark it as done when complete\n\n3. After implementing each item, verify:\n - Code follows Hard Rules from CLAUDE.md\n - SQL is in repos/ only, parameterized, uses user_conn()\n - Pydantic models used for all request/response\n - No Google dependencies introduced\n - Security checklist items for this area are satisfied (check docs/aide_security_checklist.md)\n\n4. Run tests after each logical group of changes.\n\n5. At the end, write a build log to `docs/program_management/build_log/PHASE_X_Y_<NAME>.md`:\n - Filename format: `PHASE_0_1_INFRASTRUCTURE.md`, `PHASE_1_2_DATA_MODEL.md`, etc.\n - Include:\n - **Summary**: What was implemented\n - **What Was Built**: List of files created/modified with descriptions\n - **Security Checklist Compliance**: Which items were satisfied\n - **File Structure**: Tree of new/modified files\n - **Verification**: Lint, format, test results\n - **Next Steps**: What remains in the launch plan\n - **Status**: `✅ Phase X.Y Complete` with date\n\n6. Update the launch plan checkbox items to `[x]` for completed work.\n\n## Important context per phase\n\n- **Phase 0 (Foundation):** ✅ Complete. 0.1 Infrastructure (Railway, Neon, CI/CD). 0.2 Auth (magic links via Resend, JWT cookies, RLS).\n\n- **Phase 1 (Core Product):**\n - 1.1 Kernel: Primitives, reducer, renderer, assembly. Existing code in `engine/kernel/`.\n - 1.2 Data Model: Neon Postgres with RLS. Follow `docs/infrastructure/aide_data_access.md` patterns exactly.\n - 1.3 L2/L3 Orchestrator: L2 (Haiku) compiles intent → primitives. L3 (Sonnet) synthesizes schemas, handles images.\n - 1.4 Web Chat UI: Full-viewport preview + floating chat overlay. See `docs/prds/aide_editor_prd.md`.\n - 1.5 Signal Ear: signal-cli-rest-api on Railway. Core differentiator — \"update your page from a text.\"\n - 1.6 Published Page Serving: R2 static hosting via Cloudflare CDN. `/s/{slug}` route.\n - 1.7 Reliability: Validation catches bad primitives. Retry logic. Event log is source of truth.\n\n- **Phase 2 (Rate Limiting + Engine):** Turn counting per-user (50/week free), weekly reset. Host engine files on R2 for distribution.\n\n- **Phase 3 (Payments):** Stripe Checkout for $10/mo Pro. Webhook handlers must verify signatures. Idempotent.\n\n- **Phase 4 (Landing & Launch):** Landing page at toaide.com. Seed templates. Launch checklist (Sentry, ToS, robots.txt).\n\n- **Phase 5 (Distribution):** Post-launch. Claude.ai Project, Claude Code skill, MCP server, Cowork plugin.", "variables": [], "notes": "Implement the next phase from docs/program_management/aide_launch_plan.md.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/zcancio/aide", "path": ".claude/commands/implement-phase.md", "ref": "d17e2e015961eb0e2d6613e2349fa26f20190e0b", "url": "https://github.com/zcancio/aide/blob/d17e2e015961eb0e2d6613e2349fa26f20190e0b/.claude/commands/implement-phase.md", "key": "zcancio/aide/.claude/commands/implement-phase.md" } } }

implement-phase

About

Process

Important context per phase

Install implement-phase and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews