feat(execution-plan): iterative improvements from 5 external AI test cycles#145
Merged
garrity-miepub merged 3 commits intomainfrom Mar 23, 2026
Merged
feat(execution-plan): iterative improvements from 5 external AI test cycles#145garrity-miepub merged 3 commits intomainfrom
garrity-miepub merged 3 commits intomainfrom
Conversation
…cycles
Refined the AI-driven migration execution plan through 5 iterative test
cycles, each validated by running an external AI (Claude Opus 4.6) against
a sandbox copy of timeharbor-app. Results improved from ~55% single-pass
completion (Tests 1-3) to 75% (Test 4) to 100% (Test 5).
Changes made across iterations:
1. AI Callout Block (6 rules)
- Enforce exact template structure (no reorganizing or merging sections)
- Mandate checkbox format for Steps Completed (no narrative replacement)
- Warn about commonly-skipped sections (Export Availability, Pattern
Audit, Import Map, Compliance Summary)
2. Required Companion Files section
- Documents reading order: tailwind4-integration, component-policy,
then execution-plan
3. Checkpoint after Step 4 (~50% complete)
- Root cause: AI treated component replacement as the full migration
and stopped. Checkpoint warning forces continuation through Steps 5-10.
4. cn() warning at top of Step 6
- Root cause: Clean Up header signaled low-priority work, causing AI
to skip cn() migration and jump to wrapper deletion. Warning says
Do Step 6.1 FIRST.
5. Checkpoint after Step 6 (~75% complete)
- Root cause: After wrapper deletion the AI felt done. Second checkpoint
reminds Steps 7-9 (accessibility, testing, gap detection) are audits,
not optional cleanup.
6. Step 10 enriched migration report template
- 15+ sections: Project Profile, Export Availability, Wrapper File Audit,
Pattern Audit (4 sub-tables), Steps Completed (17 pre-populated
checkboxes), Post-Migration Import Map, Files Modified/Created/Deleted,
Compliance Summary, Known Gaps, Notes
- Pre-populated all 17 step checkboxes (replaced ...etc)
- Real before/after metrics required (no X/Y placeholders)
7. AI Agent Instructions rules 8-11
- Create report file at start of Step 10
- Update incrementally as work progresses
- Use exact template structure
- Do not skip aggregated sections
Test 5 result: 100% single-pass completion. All 10 steps executed,
56/57 wrappers deleted, cn() migrated, icons audited, accessibility
checked, compliance audit run, and a fully template-compliant migration
report generated.
There was a problem hiding this comment.
Pull request overview
This PR refines the AI/human-facing @mieweb/ui migration execution plan to improve completion rates in external AI-driven migration runs by adding stricter agent instructions, mid-plan checkpoints, and a detailed, standardized migration report template.
Changes:
- Added an “AI Agent — Read This First” rules block plus clarified required companion-file reading order.
- Inserted “50%” and “75%” checkpoints and a warning to prevent skipping Step 6.1 (
cn()migration). - Introduced an expanded Step 10 migration report template and reinforced report-writing rules in the AI agent instructions.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Addresses Copilot review comment on PR #145: Step 8.3 audits raw <table> elements but the Step 10 Compliance Summary template had no corresponding row to record that metric. Added the missing row to keep the audit commands and report template in sync. This is the only change from the Copilot review we accepted. Comments #1 (Step 10 intro wording) and #3 (rule #8 append vs checkbox) were reviewed and intentionally skipped — see PR comments for rationale.
Deploying ui with
|
| Latest commit: |
af8b40b
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d21f9287.ui-6d0.pages.dev |
| Branch Preview URL: | https://feature-execution-plan-updat.ui-6d0.pages.dev |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…rkflow Updated the "Migrating Your App to MIE Web UI" section to reflect the process we validated through 5 iterative test cycles: 1. Replaced generic "share the execution-plan.md" instructions with a prominent numbered callout showing all 3 required files in order: - tailwind4-integration.md (CSS variables, theme block) - component-policy.md (126+ component catalog) - execution-plan.md (10-step procedure) Each file links directly to GitHub for easy access. 2. Added the exact prompt that produced 100% single-pass completion: "Migrate this project to @mieweb/ui following the execution plan. Work step by step, create the migration report first, and update it after each step." 3. Added Step 10 (Migration Report) card — was missing from the previous 9-step grid. Highlighted with blue border as the key deliverable. 4. Added "What You'll Get" callout documenting the 8 sections of the structured MIEWEB-UI-MIGRATION.md report the process generates. 5. Restructured "Supporting Guides" into "Additional Guides" — moved tailwind4-integration.md and component-policy.md up to the required files box (where they belong), keeping only adopting-mieweb-ui.md and compliance-prompt.md as optional reference. 6. Updated Step 6 description to explicitly mention cn() migration (key discovery from testing).
Contributor
Author
|
Updated the migration instructions to follow the steps that successfully recreated the install and component migration to mie ui. 
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refined the AI-driven migration execution plan through 5 iterative test cycles, each validated by running an external AI (Claude Opus 4.6) against a sandbox copy of timeharbor-app. Results improved from ~55% single-pass completion (Tests 1-3) to 75% (Test 4) to 100% (Test 5).
Changes made across iterations:
AI Callout Block (6 rules)
Required Companion Files section
Checkpoint after Step 4 (~50% complete)
cn() warning at top of Step 6
Checkpoint after Step 6 (~75% complete)
Step 10 enriched migration report template
AI Agent Instructions rules 8-11
Test 5 result: 100% single-pass completion. All 10 steps executed, 56/57 wrappers deleted, cn() migrated, icons audited, accessibility checked, compliance audit run, and a fully template-compliant migration report generated.