Skip to content

Update phase-2 plan and README for boxel-cli integration and issue-driven loop#4353

Open
habdelra wants to merge 3 commits intomainfrom
phase-2-plan-refinements
Open

Update phase-2 plan and README for boxel-cli integration and issue-driven loop#4353
habdelra wants to merge 3 commits intomainfrom
phase-2-plan-refinements

Conversation

@habdelra
Copy link
Copy Markdown
Contributor

@habdelra habdelra commented Apr 8, 2026

Summary

  • Rewrite phase-2-plan.md with boxel-cli integration architecture, issue-driven loop, and validation phase
  • Rewrite software-factory README.md with updated intro, prerequisites, and E2E usage instructions

Phase-2 plan changes

  • boxel-cli owns entire Boxel API surface — architectural principle, realm-operations migration table
  • Full auth lifecycle (CS-10642) — boxel-cli manages all tokens, factory never touches JWTs
  • Tool delegation (CS-10670) — boxel-cli publishes tool definitions, factory consumes via getToolDefinitions()
  • Skill alignment (CS-10613) — dedup skills, consistent homes, new boxel-api skill
  • Schema refinement (CS-10671) — Ticket → Issue rename, trim unused fields, add blockedBy/order
  • Two-level loop (CS-10672) — outer loop (issues) + inner loop (iterations with validation)
  • Validation phase (CS-10675) — parse, lint, evaluate, instantiate, run tests after every inner-loop iteration
  • Bootstrap as seed issue (CS-10673) — bootstrap becomes first issue in the loop
  • Durable clarification (CS-10674) — request_clarification creates blocking issues
  • MCP server as future evolution for tool discovery
  • Federated search scoped to /_federated-search only

README changes

  • Rewrite intro: four-phase factory flow (intake → bootstrap → implement → verify)
  • Add realm roles and artifact structure table
  • Simplify prerequisites to mise run dev-all + credentials + OpenRouter key
  • Add "Running the Factory" with full command and expected output
  • Remove stale Commands and factory:go sections

Test plan

  • pnpm --filter software-factory lint passes (js, types, format)
  • Doc review for accuracy and completeness

🤖 Generated with Claude Code

…n loop, and validation phase

Phase-2 plan updates:
- Add architectural principle: boxel-cli owns entire Boxel API surface
- Add realm-operations.ts migration table (20 functions → boxel-cli)
- Add boxel-cli full auth lifecycle (CS-10642) replacing --jwt approach
- Add tool delegation section (CS-10670): boxel-cli publishes tool definitions
- Add MCP server as future evolution for tool discovery
- Add skill alignment section (CS-10613): dedup, consistent homes, boxel-api skill
- Add schema refinement: Ticket → Issue rename, trim unused fields, add blockedBy/order
- Add validation phase after every inner-loop iteration (parse, lint, evaluate, instantiate, test)
- Rewrite orchestrator as two-level loop (outer: issues, inner: iterations with validation)
- Scope federated search to /_federated-search only
- Add Linear project reference for "Incorporate Boxel CLI to Monorepo"
- Reference all new tickets (CS-10666–CS-10677)

README updates:
- Rewrite intro to describe the four-phase factory flow
- Add realm roles and artifact structure
- Simplify prerequisites
- Add "Running the Factory" section with full E2E command and expected output
- Remove stale Commands section

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@habdelra habdelra requested a review from a team April 8, 2026 01:04
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1395e995e8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@habdelra habdelra requested a review from Copilot April 8, 2026 01:15
…alidation failure

- README: Move credentials to pre-exported env vars with read -s for password
  instead of inlining secrets in the command example
- Phase-2 plan: Break inner loop after creating fix issues so the outer loop
  picks them up, preventing duplicate fix issue generation

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the software-factory documentation to reflect the Phase 2 direction (boxel-cli integration, issue-driven scheduling, and a per-iteration validation pipeline) and to refresh the package README with current end-to-end usage guidance.

Changes:

  • Rewrites docs/phase-2-plan.md to describe an issue-driven outer/inner loop with an orchestrator-owned validation phase and boxel-cli integration boundaries.
  • Rewrites README.md to explain the factory’s phases, target-realm artifact layout, prerequisites, and an example pnpm factory:go run with expected output.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.

File Description
packages/software-factory/README.md Refreshes overview, prerequisites, and “Running the Factory” instructions plus expected CLI/UI outputs.
packages/software-factory/docs/phase-2-plan.md Updates Phase 2 plan with validation-after-each-iteration design and expanded boxel-cli integration/delegation architecture notes.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

- README: Use "ticket" consistently (Phase 1 terminology)
- Phase-2 plan: Use enum priorities (high/medium/low) instead of numeric
- Phase-2 plan: Validation failures iterate in inner loop (feed back as
  context) instead of creating fix issues. Agent can create issues via
  tool calls if it decides to.
- Phase-2 plan: Fix inconsistency about who runs tests — orchestrator
  owns validation, delegates implementation to agent
- Phase-2 plan: Update Core Idea to include validation step
- Phase-2 plan: Update orchestrator pseudocode to match

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants