feat(ai-autopilot): modes via conditions frontmatter (#244)#250
Merged
Conversation
A stem.<variant>.md sibling with metadata.conditions overrides its stem.md base
when those modes are active. loadDomainPreset(dir, { modes }) resolves the winner
per stem (most specific eligible, else base). Software Development preset gains a
technical variant of its major-change loop. Simple fan-out; #245 is the compose
follow-up.
Closes #244
suleimansh
added
enhancement
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
1 participant
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.
Last piece of the Open Loop first slice (#204): the two modes (Autopilot / Technical Control) as
conditionsfrontmatter on sibling .md files.stem.<variant>.mdfile withmetadata.conditions(a mode or list) overrides itsstem.mdbase when those modes are active. Grouping is by filename stem (name before the first dot), matching your sketch.loadDomainPreset(dir, { modes })/softwareDevelopmentPreset({ modes })resolve the winner per stem: most-specific eligible variant, else the base.selectWinnersis the pure, tested resolver.major-change.technical.mdvariant (leaner chain) as a live example.Two small calls, flagging:
conditionslives undermetadata(likeon/run/url), since the frontmatter schema strips unknown top-level keys. Your Open Loop: customizable prompts + flows, domain presets, marketplace #204 sketch wrote it top-level; same idea, just namespaced.The UI checkboxes ([ ] Autopilot [ ] Technical) are framework-side and out of scope here. Follow-up #245 (compose prompts from params) only if variants get too duplicative.
Tests: 23 preset tests (conditions resolver + mode-aware load + shipped-preset override). Typecheck (21 projects) green; 311 package tests, the one failure is the pre-existing docker flake. Changeset: minor.
Closes #244