feat(ultraplan-local): v1.6.0 — /ultraresearch-local deep research command
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:
commit
4679f4556d
38 changed files with 6708 additions and 0 deletions
64
templates/spec-template.md
Normal file
64
templates/spec-template.md
Normal file
|
|
@ -0,0 +1,64 @@
|
|||
# Task: {title}
|
||||
|
||||
## Goal
|
||||
|
||||
What success looks like. One clear paragraph.
|
||||
|
||||
## Non-Goals
|
||||
|
||||
What is explicitly out of scope for this task.
|
||||
|
||||
- {non-goal 1}
|
||||
- {non-goal 2}
|
||||
|
||||
## Constraints
|
||||
|
||||
Technical, time, or resource limitations.
|
||||
|
||||
- {constraint 1}
|
||||
- {constraint 2}
|
||||
|
||||
## Preferences
|
||||
|
||||
Preferred patterns, frameworks, libraries, or approaches.
|
||||
|
||||
- {preference 1}
|
||||
- {preference 2}
|
||||
|
||||
## Non-Functional Requirements
|
||||
|
||||
Performance, security, accessibility, scalability, or other quality attributes.
|
||||
|
||||
- {NFR 1}
|
||||
- {NFR 2}
|
||||
|
||||
## Success Criteria
|
||||
|
||||
Falsifiable conditions that define "done". Each must be checkable by running a
|
||||
command or observing a specific system behavior.
|
||||
|
||||
- {criterion — e.g., "All existing tests pass: `npm test` exits 0"}
|
||||
- {criterion — e.g., "New endpoint returns 200: `curl -s localhost:3000/api/health | jq .status` → "ok""}
|
||||
- {criterion — e.g., "No TypeScript errors: `npx tsc --noEmit` exits 0"}
|
||||
|
||||
Do NOT write vague criteria:
|
||||
- "It should work" (not testable)
|
||||
- "The feature is implemented" (not falsifiable)
|
||||
- "Performance is acceptable" (no baseline given)
|
||||
|
||||
## Prior Attempts
|
||||
|
||||
What has been tried before and what happened. Leave blank if this is a fresh task.
|
||||
|
||||
## Open Questions
|
||||
|
||||
Unresolved items that may affect the plan. Flag these as assumptions if proceeding
|
||||
without answers.
|
||||
|
||||
- {question 1}
|
||||
|
||||
## Metadata
|
||||
|
||||
- **Created:** {YYYY-MM-DD}
|
||||
- **Mode:** {interview | manual}
|
||||
- **Source:** {ultraplan interview | user-provided}
|
||||
Loading…
Add table
Add a link
Reference in a new issue