feat(ultraplan-local): v2.2.0 — /ultra-cc-architect-local
New optional command between /ultraresearch-local and /ultraplan-local that matches brief+research against Claude Code features (hooks, subagents, skills, output-styles, MCP, plan-mode, worktrees, background-agents) and produces an architecture note with brief-anchored rationale plus explicit gaps. Added: - commands/ultra-cc-architect-local.md (--project, --fg, --quick, --no-gaps) - agents/architect-orchestrator.md (opus) — 6-phase background orchestrator - agents/feature-matcher.md (sonnet) — fallback-ranked feature proposals - agents/gap-identifier.md (sonnet) — 4 gap classes with issue-ready drafts - agents/architecture-critic.md (sonnet) — hallucination gate as BLOCKER - skills/cc-architect-catalog/ — SKILL.md + 10 seed entries (reference/pattern) Changed (non-breaking): - commands/ultraplan-local.md — auto-discovers architecture/overview.md - agents/planning-orchestrator.md — cross-references cc_features_proposed - plugin.json — 2.1.0 → 2.2.0, description, cc-architecture keyword - CHANGELOG, README, CLAUDE.md (plugin + marketplace root) Pipeline becomes brief → research → architect → plan → execute. Architect is optional; existing project dirs keep working unchanged. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
parent
23aaaa6e6c
commit
2da95b3cd3
24 changed files with 2325 additions and 28 deletions
|
|
@ -66,6 +66,12 @@ You will receive a prompt containing:
|
|||
- **Research briefs** (optional) — paths to research briefs. Includes both
|
||||
auto-discovered `{project_dir}/research/*.md` files and any explicit briefs
|
||||
passed via `--research`. Read each brief before launching exploration agents.
|
||||
- **Architecture note** (optional) — path to `{project_dir}/architecture/overview.md`
|
||||
produced by the optional `/ultra-cc-architect-local` command. When provided,
|
||||
this note proposes CC features (hooks, subagents, skills, MCP, etc.) the
|
||||
implementation should lean on, with brief-anchored rationale and a coverage-
|
||||
gap section. Missing file is fine — this is additive context, not a
|
||||
requirement. Value is either an absolute path or `"none"`.
|
||||
|
||||
Read the brief file first. It is the contract that bounds your work. Parse its
|
||||
frontmatter (`task`, `slug`, `project_dir`, `research_topics`, `research_status`)
|
||||
|
|
@ -75,6 +81,12 @@ Success Criteria, Research Plan, Open Questions, Prior Attempts).
|
|||
If research briefs are provided, read those too — they contain pre-built context
|
||||
for the research topics the brief declared.
|
||||
|
||||
If an architecture note is provided (path != "none"), read it before launching
|
||||
exploration agents. Treat its `cc_features_proposed` list as **priors**, not
|
||||
mandates — exploration may contradict or override with evidence from the
|
||||
codebase. Surface the architecture note's Open Questions inside your synthesis
|
||||
so the plan addresses them.
|
||||
|
||||
## Your workflow
|
||||
|
||||
Execute these phases in order. Do not skip phases.
|
||||
|
|
@ -183,8 +195,15 @@ Synthesize all findings:
|
|||
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
|
||||
8. **Map brief sections → plan sections:**
|
||||
7. **If an architecture note is provided:** cross-reference agent findings with
|
||||
the note's `cc_features_proposed`. For each proposed feature, check whether
|
||||
exploration confirms or contradicts the rationale. Proposed features that the
|
||||
codebase already uses well → adopt in plan. Proposed features that conflict
|
||||
with codebase patterns → surface the conflict in the plan's Alternatives
|
||||
Considered section and choose based on evidence, not the note alone. Include
|
||||
the note's Coverage gaps in Risks and Mitigations when relevant to the task.
|
||||
8. Note remaining gaps as explicit assumptions
|
||||
9. **Map brief sections → plan sections:**
|
||||
- Brief Intent → plan Context (motivation paragraph)
|
||||
- Brief Goal → plan Context (end state)
|
||||
- Brief Constraints/Preferences/NFRs → inputs to Implementation Plan decisions
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue