-
Notifications
You must be signed in to change notification settings - Fork 0
Feature/multi agent taskid collab 20251114 #58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
bb938c9
chore(publish): use prepack for auto-build; restore explicit bin map …
crazygo b64fa94
fix(bin): keep only 'taskagent' CLI name; remove extra alias
crazygo b41ae8b
refactor(package.json): simplify bin entry for taskagent CLI
crazygo 5e3210b
feat: Rebuild Multi-Agent Communication Demo and Refactor Imports
crazygo a86aafc
refactor(FeatureWriterAgent): remove unused imports
crazygo c97158a
feat: add planned upgrade for Feature-Updater Sequential Agent with n…
crazygo 874a38a
feat: add additional agent evolution details to README for improved u…
crazygo 03e4360
feat: add vite-tsconfig-paths and related dependencies for improved T…
crazygo 672f52c
fix: add vite peer dependency to resolve CI test failures
crazygo File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
59 changes: 59 additions & 0 deletions
59
.askman/tasks/20251114-2255-rebuild-multi-agent-comm-demo/README.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,59 @@ | ||
| # Rebuild Multi-Agent Communication (Quick Dev Flow Demo) | ||
|
|
||
| ## Requirement (2025-11-14T16:13:10.912Z) | ||
| - The Feature-Plan stage MUST support interrupt/abort when it detects conflicts with existing requirements. | ||
| - On interrupt, the sequential pipeline MUST short-circuit and emit a structured failure payload (e.g., { ok: false, code: 'CONFLICT', message, details }) or a controlled abort that the orchestrator maps to a failure, preventing downstream stages (feature-edit, YAML validator, report). | ||
|
|
||
| - Task ID: 20251114-2255-rebuild-multi-agent-comm-demo | ||
| - Goal: Rebuild/streamline multi-agent communication (DevHub ↔ LoopAgent/SequentialAgent) for a quick development flow demo. | ||
| - Notes: | ||
| - Focus on task-id centric collaboration across agents | ||
| - Keep CLI UX stable; prefer npx usage | ||
| - Prepare minimal demo path via DevHub + Blueprint + Coder/Review | ||
|
|
||
| ## Additional Notes (2025-11-14T15:00:15.263Z) | ||
| - Atomic agent types: Prompt Agent and Programming Agent | ||
| - Prompt Agent is prompt-driven, focusing on a specific task type's working method | ||
| - Programming Agent can have multiple nodes; nodes are connected via program logic, and can be defined so each node can be emitted independently | ||
|
|
||
| ## Design Target & Use Case (2025-11-14T15:08:00.563Z) | ||
| - Agent design is centered on artifacts + working method, not just raw prompts. | ||
| - Use Case: feature-updater agent | ||
| - Goal: After edits, ensure features.yaml remains well-structured. | ||
| - Validate: No duplicate or conflicting feature entries (避免重复/冲突). | ||
| - Problem with pure Prompt Agent: LLM can introduce subtle structural mistakes that propagate downstream. | ||
| - Decision: Use Programming Agent architecture (multi-node, logic-enforced) to guarantee deterministic validation & merge rules before committing updates. | ||
| - Rationale: Programming Agent nodes can emit structured events (parse, diff, validate, normalize) ensuring post-edit artifact integrity and reducing cascading errors in later workflow stages. | ||
|
|
||
| ## Code Review By Features Agent (2025-11-14T15:40:26.943Z) | ||
| - Purpose: Verify whether new code changes (commit diffs) risk breaking previously implemented features. | ||
| - Context: When adding new features quickly, we validate the new one but often skip deep regression of old ones. | ||
| - Approach: Iterate existing features (from features.yaml or feature artifacts) and cross-check each feature's logic paths against changed code segments. | ||
| - Detection: Identify overlaps (cross points) where modified functions, modules, or data contracts intersect a feature's required invariants. | ||
| - Output: Structured report listing per-feature risk status, with: | ||
| - feature_id / name | ||
| - risk_level (none/low/medium/high) | ||
| - impacted elements (files, functions, lines) | ||
| - rationale (what change introduces the potential break) | ||
| - Architecture Choice: Programming Agent (multi-node) for deterministic traversal: nodes = [collect_diff, enumerate_features, map_dependencies, detect_cross, score_risk, generate_report]. | ||
| - Benefit: Early surfacing of silent regressions without full test suite expansion. | ||
|
|
||
| ## Planned Upgrade: Feature-Updater Sequential Agent (2025-11-14T15:59:12.767Z) | ||
| - Goal: Upgrade to feature-updater with a sequential architecture; rename feature-writer to feature-edit. | ||
| - Composition: | ||
| - Feature-Plan (Prompt Agent; new agent) | ||
| - Loop (LoopAgent; current: blueprint loop) | ||
| - Stage: feature-edit (Prompt Agent; renamed from feature-writer; supports add/delete/change) → YAML validator | ||
| - Feature-Changes Review (Prompt Agent) to check and produce a report | ||
| - Pipeline: feature-plan → loop(feature-edit → yaml validator) → feature-changes report. | ||
| - Rationale: Combine prompt-driven ideation with programmatic validation to reduce LLM-induced structural errors while producing a final human-readable risk/change report. | ||
|
|
||
| > 2025-11-14T16:00:41.950Z: Note — feature-edit is a Prompt Agent. | ||
|
|
||
| ## Additional Agent Evolution (2025-11-14T16:21:31.043Z) | ||
| - Blueprint will become a Prompt Agent (was LoopAgent) focused on direct user dialogue and selectively invoking other agents when needed (not a full orchestrator/central workflow controller). | ||
| - Selection logic: interpret user intent → choose Feature-Updater, UI Review, Notes Agent, or others; skip calls when no added value. | ||
| - UI Review (ui-review) remains a Prompt Agent for UI/UX; legacy structure requires audit/refactor. | ||
| - Notes Agent (new Prompt Agent): writes fragments to notes-<timestamp>.md in task workspace; appends decisions, conflicts, risks chronologically. | ||
| - Example interaction path: user intent → blueprint (dialog) → conditional calls: (feature-updater loop) and/or (ui-review) → notes-agent summary. | ||
| - Abort policy: On conflict detected in feature-plan or validation failure, blueprint stops further calls and invokes notes-agent to persist the issue. |
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -33,6 +33,7 @@ coverage/ | |
|
|
||
| # Bundlers and frameworks | ||
| .parcel-cache/ | ||
| .vite-cache/ | ||
| .next/ | ||
| .nuxt/ | ||
| .svelte-kit/ | ||
|
|
||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This relative import should be updated to use the new path alias
@execution/TabExecutor.jsinstead of../../execution/TabExecutor.jsto be consistent with the rest of the PR's refactoring.