open/ktg-plugin-marketplace
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity Actions

feat(ultraplan-local): v1.6.0 — /ultraresearch-local deep research command

Browse source 
Add /ultraresearch-local for structured research combining local codebase
analysis with external knowledge via parallel agent swarms. Produces research
briefs with triangulation, confidence ratings, and source quality assessment.

New command: /ultraresearch-local with modes --quick, --local, --external, --fg.
New agents: research-orchestrator (opus), docs-researcher, community-researcher,
security-researcher, contrarian-researcher, gemini-bridge (all sonnet).
New template: research-brief-template.md.

Integration: --research flag in /ultraplan-local accepts pre-built research
briefs (up to 3), enriches the interview and exploration phases. Planning
orchestrator cross-references brief findings during synthesis.

Design principle: Context Engineering — right information to right agent at
right time. Research briefs are structured artifacts in the pipeline:
ultraresearch → brief → ultraplan --research → plan → ultraexecute.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-04-08 08:58:35 +02:00
commit 5be9c8e47c
27 changed files with 1723 additions and 73 deletions
Download patch file Download diff file Expand all files Collapse all files

26
plugins/ultraplan-local/agents/planning-orchestrator.md
View file

@ -59,8 +59,12 @@ You will receive a prompt containing:
- **Plan file destination** — where to write the plan
- **Plugin root** — for template access
- **Mode** (optional) — if `mode: quick`, skip the agent swarm and use lightweight scanning
- **Research briefs** (optional) — paths to ultraresearch-local briefs. When present,
these provide pre-built research context that should inform exploration and planning.
Read each brief before launching exploration agents.
Read the spec file first. It defines the scope of your work.
If research briefs are provided, read those too — they contain pre-built context.
## Your workflow
@ -129,10 +133,25 @@ for medium+ codebases only. Pass the task description as context.
**research-scout** — launch conditionally if the task involves technologies, APIs,
or libraries that are not clearly present in the codebase, being upgraded to a new
major version, or being used in an unfamiliar way.
major version, or being used in an unfamiliar way. **If research briefs are provided:**
check whether the technology is already covered in the brief. Only launch research-scout
for technologies NOT covered by the brief.
For each agent, pass the task description and relevant context from the spec.
### Research-enriched exploration
When research briefs are provided, inject a summary into each agent's prompt:
> "Pre-existing research is available for this task. Key findings:
> {2-3 sentence summary of the brief's executive summary and synthesis}.
> Focus your exploration on areas NOT covered by this research.
> Validate or contradict research claims where your findings overlap."
Do NOT inject the full brief into sub-agent prompts — it would consume too much
context. Summarize to 2-3 sentences per brief. The orchestrator (you) holds the
full brief in context for synthesis.
### Phase 3 — Targeted deep-dives
Review all agent results. Identify knowledge gaps — areas too shallow for confident
@ -148,7 +167,10 @@ Synthesize all findings:
3. Build complete codebase mental model
4. Catalog reusable code
5. Integrate research findings (mark source: codebase vs. research)
6. Note remaining gaps as explicit assumptions
6. **If research briefs provided:** cross-reference agent findings with pre-existing
brief. Flag agreements (increases confidence) and contradictions (needs resolution).
Incorporate brief recommendations into planning context.
7. Note remaining gaps as explicit assumptions
Internal context only — do not write to disk.