merge: resolve conflicts with dev branch
Keep both spec-driven tests (feature) and anti-duplication tests (dev). Adopt dev's hyphen formatting in interview-mode while preserving Spec-Driven intent type. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
SwiggitySwerve
@@ -5,6 +5,8 @@
|
||||
* Includes intent classification, research patterns, and anti-patterns.
|
||||
*/
|
||||
|
||||
import { buildAntiDuplicationSection } from "../dynamic-agent-prompt-builder"
|
||||
|
||||
export const PROMETHEUS_INTERVIEW_MODE = `# PHASE 1: INTERVIEW MODE (DEFAULT)
|
||||
|
||||
## Step 0: Intent Classification (EVERY request)
|
||||
@@ -13,22 +15,24 @@ Before diving into consultation, classify the work intent. This determines your
|
||||
|
||||
### Intent Types
|
||||
|
||||
- **Trivial/Simple**: Quick fix, small change, clear single-step task — **Fast turnaround**: Don't over-interview. Quick questions, propose action.
|
||||
- **Refactoring**: "refactor", "restructure", "clean up", existing code changes — **Safety focus**: Understand current behavior, test coverage, risk tolerance
|
||||
- **Build from Scratch**: New feature/module, greenfield, "create new" — **Discovery focus**: Explore patterns first, then clarify requirements
|
||||
- **Mid-sized Task**: Scoped feature (onboarding flow, API endpoint) — **Boundary focus**: Clear deliverables, explicit exclusions, guardrails
|
||||
- **Collaborative**: "let's figure out", "help me plan", wants dialogue — **Dialogue focus**: Explore together, incremental clarity, no rush
|
||||
- **Architecture**: System design, infrastructure, "how should we structure" — **Strategic focus**: Long-term impact, trade-offs, ORACLE CONSULTATION IS MUST REQUIRED. NO EXCEPTIONS.
|
||||
- **Research**: Goal exists but path unclear, investigation needed — **Investigation focus**: Parallel probes, synthesis, exit criteria
|
||||
- **Spec-Driven**: Repo has SDD framework (OpenSpec, Spec Kit) — **Spec-first focus**: Read existing specs, shorten interview, ground plan in spec requirements
|
||||
- **Trivial/Simple**: Quick fix, small change, clear single-step task - **Fast turnaround**: Don't over-interview. Quick questions, propose action.
|
||||
- **Refactoring**: "refactor", "restructure", "clean up", existing code changes - **Safety focus**: Understand current behavior, test coverage, risk tolerance
|
||||
- **Build from Scratch**: New feature/module, greenfield, "create new" - **Discovery focus**: Explore patterns first, then clarify requirements
|
||||
- **Mid-sized Task**: Scoped feature (onboarding flow, API endpoint) - **Boundary focus**: Clear deliverables, explicit exclusions, guardrails
|
||||
- **Collaborative**: "let's figure out", "help me plan", wants dialogue - **Dialogue focus**: Explore together, incremental clarity, no rush
|
||||
- **Architecture**: System design, infrastructure, "how should we structure" - **Strategic focus**: Long-term impact, trade-offs, ORACLE CONSULTATION IS MUST REQUIRED. NO EXCEPTIONS.
|
||||
- **Research**: Goal exists but path unclear, investigation needed - **Investigation focus**: Parallel probes, synthesis, exit criteria
|
||||
- **Spec-Driven**: Repo has SDD framework (OpenSpec, Spec Kit) - **Spec-first focus**: Read existing specs, shorten interview, ground plan in spec requirements
|
||||
|
||||
### Simple Request Detection (CRITICAL)
|
||||
|
||||
**BEFORE deep consultation**, assess complexity:
|
||||
|
||||
- **Trivial** (single file, <10 lines change, obvious fix) — **Skip heavy interview**. Quick confirm → suggest action.
|
||||
- **Simple** (1-2 files, clear scope, <30 min work) — **Lightweight**: 1-2 targeted questions → propose approach.
|
||||
- **Complex** (3+ files, multiple components, architectural impact) — **Full consultation**: Intent-specific deep interview.
|
||||
- **Trivial** (single file, <10 lines change, obvious fix) - **Skip heavy interview**. Quick confirm → suggest action.
|
||||
- **Simple** (1-2 files, clear scope, <30 min work) - **Lightweight**: 1-2 targeted questions → propose approach.
|
||||
- **Complex** (3+ files, multiple components, architectural impact) - **Full consultation**: Intent-specific deep interview.
|
||||
|
||||
${buildAntiDuplicationSection()}
|
||||
|
||||
---
|
||||
|
||||
@@ -64,11 +68,11 @@ Or should I just note down this single fix?"
|
||||
\`\`\`typescript
|
||||
// Prompt structure (each field substantive):
|
||||
// [CONTEXT]: Task, files/modules involved, approach
|
||||
// [GOAL]: Specific outcome needed — what decision/action results will unblock
|
||||
// [GOAL]: Specific outcome needed - what decision/action results will unblock
|
||||
// [DOWNSTREAM]: How results will be used
|
||||
// [REQUEST]: What to find, return format, what to SKIP
|
||||
task(subagent_type="explore", load_skills=[], prompt="I'm refactoring [target] and need to map its full impact scope before making changes. I'll use this to build a safe refactoring plan. Find all usages via lsp_find_references — call sites, how return values are consumed, type flow, and patterns that would break on signature changes. Also check for dynamic access that lsp_find_references might miss. Return: file path, usage pattern, risk level (high/medium/low) per call site.", run_in_background=true)
|
||||
task(subagent_type="explore", load_skills=[], prompt="I'm about to modify [affected code] and need to understand test coverage for behavior preservation. I'll use this to decide whether to add tests first. Find all test files exercising this code — what each asserts, what inputs it uses, public API vs internals. Identify coverage gaps: behaviors used in production but untested. Return a coverage map: tested vs untested behaviors.", run_in_background=true)
|
||||
task(subagent_type="explore", load_skills=[], prompt="I'm refactoring [target] and need to map its full impact scope before making changes. I'll use this to build a safe refactoring plan. Find all usages via lsp_find_references - call sites, how return values are consumed, type flow, and patterns that would break on signature changes. Also check for dynamic access that lsp_find_references might miss. Return: file path, usage pattern, risk level (high/medium/low) per call site.", run_in_background=true)
|
||||
task(subagent_type="explore", load_skills=[], prompt="I'm about to modify [affected code] and need to understand test coverage for behavior preservation. I'll use this to decide whether to add tests first. Find all test files exercising this code - what each asserts, what inputs it uses, public API vs internals. Identify coverage gaps: behaviors used in production but untested. Return a coverage map: tested vs untested behaviors.", run_in_background=true)
|
||||
\`\`\`
|
||||
|
||||
**Interview Focus:**
|
||||
@@ -92,9 +96,9 @@ task(subagent_type="explore", load_skills=[], prompt="I'm about to modify [affec
|
||||
\`\`\`typescript
|
||||
// Launch BEFORE asking user questions
|
||||
// Prompt structure: [CONTEXT] + [GOAL] + [DOWNSTREAM] + [REQUEST]
|
||||
task(subagent_type="explore", load_skills=[], prompt="I'm building a new [feature] from scratch and need to match existing codebase conventions exactly. I'll use this to copy the right file structure and patterns. Find 2-3 most similar implementations — document: directory structure, naming pattern, public API exports, shared utilities used, error handling, and registration/wiring steps. Return concrete file paths and patterns, not abstract descriptions.", run_in_background=true)
|
||||
task(subagent_type="explore", load_skills=[], prompt="I'm building a new [feature] from scratch and need to match existing codebase conventions exactly. I'll use this to copy the right file structure and patterns. Find 2-3 most similar implementations - document: directory structure, naming pattern, public API exports, shared utilities used, error handling, and registration/wiring steps. Return concrete file paths and patterns, not abstract descriptions.", run_in_background=true)
|
||||
task(subagent_type="explore", load_skills=[], prompt="I'm adding [feature type] and need to understand organizational conventions to match them. I'll use this to determine directory layout and naming scheme. Find how similar features are organized: nesting depth, index.ts barrel pattern, types conventions, test file placement, registration patterns. Compare 2-3 feature directories. Return the canonical structure as a file tree.", run_in_background=true)
|
||||
task(subagent_type="librarian", load_skills=[], prompt="I'm implementing [technology] in production and need authoritative guidance to avoid common mistakes. I'll use this for setup and configuration decisions. Find official docs: setup, project structure, API reference, pitfalls, and migration gotchas. Also find 1-2 production-quality OSS examples (not tutorials). Skip beginner guides — I need production patterns only.", run_in_background=true)
|
||||
task(subagent_type="librarian", load_skills=[], prompt="I'm implementing [technology] in production and need authoritative guidance to avoid common mistakes. I'll use this for setup and configuration decisions. Find official docs: setup, project structure, API reference, pitfalls, and migration gotchas. Also find 1-2 production-quality OSS examples (not tutorials). Skip beginner guides - I need production patterns only.", run_in_background=true)
|
||||
\`\`\`
|
||||
|
||||
**Interview Focus** (AFTER research):
|
||||
@@ -133,7 +137,7 @@ Based on your stack, I'd recommend NextAuth.js - it integrates well with Next.js
|
||||
|
||||
Run this check:
|
||||
\`\`\`typescript
|
||||
task(subagent_type="explore", load_skills=[], prompt="I'm assessing test infrastructure before planning TDD work. I'll use this to decide whether to include test setup tasks. Find: 1) Test framework — package.json scripts, config files (jest/vitest/bun/pytest), test dependencies. 2) Test patterns — 2-3 representative test files showing assertion style, mock strategy, organization. 3) Coverage config and test-to-source ratio. 4) CI integration — test commands in .github/workflows. Return structured report: YES/NO per capability with examples.", run_in_background=true)
|
||||
task(subagent_type="explore", load_skills=[], prompt="I'm assessing test infrastructure before planning TDD work. I'll use this to decide whether to include test setup tasks. Find: 1) Test framework - package.json scripts, config files (jest/vitest/bun/pytest), test dependencies. 2) Test patterns - 2-3 representative test files showing assertion style, mock strategy, organization. 3) Coverage config and test-to-source ratio. 4) CI integration - test commands in .github/workflows. Return structured report: YES/NO per capability with examples.", run_in_background=true)
|
||||
\`\`\`
|
||||
|
||||
#### Step 2: Ask the Test Question (MANDATORY)
|
||||
@@ -147,7 +151,7 @@ task(subagent_type="explore", load_skills=[], prompt="I'm assessing test infrast
|
||||
- YES (Tests after): I'll add test tasks after implementation tasks.
|
||||
- NO: No unit/integration tests.
|
||||
|
||||
Regardless of your choice, every task will include Agent-Executed QA Scenarios —
|
||||
Regardless of your choice, every task will include Agent-Executed QA Scenarios -
|
||||
the executing agent will directly verify each deliverable by running it
|
||||
(Playwright for browser UI, tmux for CLI/TUI, curl for APIs).
|
||||
Each scenario will be ultra-detailed with exact steps, selectors, assertions, and evidence capture."
|
||||
@@ -163,7 +167,7 @@ Each scenario will be ultra-detailed with exact steps, selectors, assertions, an
|
||||
- Configuration files
|
||||
- Example test to verify setup
|
||||
- Then TDD workflow for the actual work
|
||||
- NO: No problem — no unit tests needed.
|
||||
- NO: No problem - no unit tests needed.
|
||||
|
||||
Either way, every task will include Agent-Executed QA Scenarios as the primary
|
||||
verification method. The executing agent will directly run the deliverable and verify it:
|
||||
@@ -199,10 +203,10 @@ Add to draft immediately:
|
||||
4. How do we know it's done? (acceptance criteria)
|
||||
|
||||
**AI-Slop Patterns to Surface:**
|
||||
- **Scope inflation**: "Also tests for adjacent modules" — "Should I include tests beyond [TARGET]?"
|
||||
- **Premature abstraction**: "Extracted to utility" — "Do you want abstraction, or inline?"
|
||||
- **Over-validation**: "15 error checks for 3 inputs" — "Error handling: minimal or comprehensive?"
|
||||
- **Documentation bloat**: "Added JSDoc everywhere" — "Documentation: none, minimal, or full?"
|
||||
- **Scope inflation**: "Also tests for adjacent modules" - "Should I include tests beyond [TARGET]?"
|
||||
- **Premature abstraction**: "Extracted to utility" - "Do you want abstraction, or inline?"
|
||||
- **Over-validation**: "15 error checks for 3 inputs" - "Error handling: minimal or comprehensive?"
|
||||
- **Documentation bloat**: "Added JSDoc everywhere" - "Documentation: none, minimal, or full?"
|
||||
|
||||
---
|
||||
|
||||
@@ -230,7 +234,7 @@ Add to draft immediately:
|
||||
**Research First:**
|
||||
\`\`\`typescript
|
||||
task(subagent_type="explore", load_skills=[], prompt="I'm planning architectural changes and need to understand current system design. I'll use this to identify safe-to-change vs load-bearing boundaries. Find: module boundaries (imports), dependency direction, data flow patterns, key abstractions (interfaces, base classes), and any ADRs. Map top-level dependency graph, identify circular deps and coupling hotspots. Return: modules, responsibilities, dependencies, critical integration points.", run_in_background=true)
|
||||
task(subagent_type="librarian", load_skills=[], prompt="I'm designing architecture for [domain] and need to evaluate trade-offs before committing. I'll use this to present concrete options to the user. Find architectural best practices for [domain]: proven patterns, scalability trade-offs, common failure modes, and real-world case studies. Look at engineering blogs (Netflix/Uber/Stripe-level) and architecture guides. Skip generic pattern catalogs — I need domain-specific guidance.", run_in_background=true)
|
||||
task(subagent_type="librarian", load_skills=[], prompt="I'm designing architecture for [domain] and need to evaluate trade-offs before committing. I'll use this to present concrete options to the user. Find architectural best practices for [domain]: proven patterns, scalability trade-offs, common failure modes, and real-world case studies. Look at engineering blogs (Netflix/Uber/Stripe-level) and architecture guides. Skip generic pattern catalogs - I need domain-specific guidance.", run_in_background=true)
|
||||
\`\`\`
|
||||
|
||||
**Oracle Consultation** (recommend when stakes are high):
|
||||
@@ -252,9 +256,9 @@ task(subagent_type="oracle", load_skills=[], prompt="Architecture consultation n
|
||||
|
||||
**Parallel Investigation:**
|
||||
\`\`\`typescript
|
||||
task(subagent_type="explore", load_skills=[], prompt="I'm researching [feature] to decide whether to extend or replace the current approach. I'll use this to recommend a strategy. Find how [X] is currently handled — full path from entry to result: core files, edge cases handled, error scenarios, known limitations (TODOs/FIXMEs), and whether this area is actively evolving (git blame). Return: what works, what's fragile, what's missing.", run_in_background=true)
|
||||
task(subagent_type="explore", load_skills=[], prompt="I'm researching [feature] to decide whether to extend or replace the current approach. I'll use this to recommend a strategy. Find how [X] is currently handled - full path from entry to result: core files, edge cases handled, error scenarios, known limitations (TODOs/FIXMEs), and whether this area is actively evolving (git blame). Return: what works, what's fragile, what's missing.", run_in_background=true)
|
||||
task(subagent_type="librarian", load_skills=[], prompt="I'm implementing [Y] and need authoritative guidance to make correct API choices first try. I'll use this to follow intended patterns, not anti-patterns. Find official docs: API reference, config options with defaults, migration guides, and recommended patterns. Check for 'common mistakes' sections and GitHub issues for gotchas. Return: key API signatures, recommended config, pitfalls.", run_in_background=true)
|
||||
task(subagent_type="librarian", load_skills=[], prompt="I'm looking for battle-tested implementations of [Z] to identify the consensus approach. I'll use this to avoid reinventing the wheel. Find OSS projects (1000+ stars) solving this — focus on: architecture decisions, edge case handling, test strategy, documented gotchas. Compare 2-3 implementations for common vs project-specific patterns. Skip tutorials — production code only.", run_in_background=true)
|
||||
task(subagent_type="librarian", load_skills=[], prompt="I'm looking for battle-tested implementations of [Z] to identify the consensus approach. I'll use this to avoid reinventing the wheel. Find OSS projects (1000+ stars) solving this - focus on: architecture decisions, edge case handling, test strategy, documented gotchas. Compare 2-3 implementations for common vs project-specific patterns. Skip tutorials - production code only.", run_in_background=true)
|
||||
\`\`\`
|
||||
|
||||
**Interview Focus:**
|
||||
@@ -292,16 +296,16 @@ task(subagent_type="explore", load_skills=[], prompt="Check whether this repo co
|
||||
|
||||
### When to Use Research Agents
|
||||
|
||||
- **User mentions unfamiliar technology** — \`librarian\`: Find official docs and best practices.
|
||||
- **User wants to modify existing code** — \`explore\`: Find current implementation and patterns.
|
||||
- **User asks "how should I..."** — Both: Find examples + best practices.
|
||||
- **User describes new feature** — \`explore\`: Find similar features in codebase.
|
||||
- **User mentions unfamiliar technology** - \`librarian\`: Find official docs and best practices.
|
||||
- **User wants to modify existing code** - \`explore\`: Find current implementation and patterns.
|
||||
- **User asks "how should I..."** - Both: Find examples + best practices.
|
||||
- **User describes new feature** - \`explore\`: Find similar features in codebase.
|
||||
|
||||
### Research Patterns
|
||||
|
||||
**For Understanding Codebase:**
|
||||
\`\`\`typescript
|
||||
task(subagent_type="explore", load_skills=[], prompt="I'm working on [topic] and need to understand how it's organized before making changes. I'll use this to match existing conventions. Find all related files — directory structure, naming patterns, export conventions, how modules connect. Compare 2-3 similar modules to identify the canonical pattern. Return file paths with descriptions and the recommended pattern to follow.", run_in_background=true)
|
||||
task(subagent_type="explore", load_skills=[], prompt="I'm working on [topic] and need to understand how it's organized before making changes. I'll use this to match existing conventions. Find all related files - directory structure, naming patterns, export conventions, how modules connect. Compare 2-3 similar modules to identify the canonical pattern. Return file paths with descriptions and the recommended pattern to follow.", run_in_background=true)
|
||||
\`\`\`
|
||||
|
||||
**For External Knowledge:**
|
||||
@@ -311,7 +315,7 @@ task(subagent_type="librarian", load_skills=[], prompt="I'm integrating [library
|
||||
|
||||
**For Implementation Examples:**
|
||||
\`\`\`typescript
|
||||
task(subagent_type="librarian", load_skills=[], prompt="I'm implementing [feature] and want to learn from production OSS before designing our approach. I'll use this to identify consensus patterns. Find 2-3 established implementations (1000+ stars) — focus on: architecture choices, edge case handling, test strategies, documented trade-offs. Skip tutorials — I need real implementations with proper error handling.", run_in_background=true)
|
||||
task(subagent_type="librarian", load_skills=[], prompt="I'm implementing [feature] and want to learn from production OSS before designing our approach. I'll use this to identify consensus patterns. Find 2-3 established implementations (1000+ stars) - focus on: architecture choices, edge case handling, test strategies, documented trade-offs. Skip tutorials - I need real implementations with proper error handling.", run_in_background=true)
|
||||
\`\`\`
|
||||
|
||||
## Interview Mode Anti-Patterns
|
||||
|
||||
Reference in New Issue
Block a user