docs(ambient): align init/CLI descriptions with keyword detection; tighten preamble directives#236
Merged
Merged
Conversation
added 2 commits
June 2, 2026 23:00
…ghten preamble directives Ambient mode gained first-word keyword detection (#235) but the init flow, ambient CLI text, plugin description, and README still described plan-only auto-detection. Update all user-facing copy to cover both detection paths (keyword + structured plan). Also tighten the two directives the preamble hook injects: symmetric structure across both paths, explicit input pass-through, and an immediately/do-not-pause instruction to preserve ambient's zero-friction intent.
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.
Summary
Ambient mode gained first-word keyword detection in #235 (prompts starting with
implement,explore,research,debug, orplaninvoke the matchingdevflow:<keyword>skill). But the init flow,devflow ambientCLI text, plugin description, and README still described plan-only auto-detection — leaving the docs out of step with the two-path hook behavior.This PR aligns all user-facing copy and tightens the directives the
preamblehook injects.Changes
Descriptions updated to cover both detection paths (keyword + structured plan):
src/cli/commands/init.ts— ambient mode prompt note +--ambientflag helpsrc/cli/commands/ambient.ts— command description, usage note, enable-success message, and a stale code commentsrc/cli/plugins.ts— ambient plugin description → "Keyword + plan auto-detection"README.md— "Ambient intelligence" line now names the keyword start words and structured plansInjected directives tightened (
scripts/hooks/preamble):Notes
preamblehook is copied to~/.devflow/scripts/atdevflow inittime, so the directive change takes effect after a re-init.Verification
npm run build:cli— passesbash -n scripts/hooks/preamble— syntax OK