refactor(agents): convert all markdown tables to bullet lists across 12 agent files
Tables in template literal prompts render poorly in some LLM contexts. Replaced 43 table instances with equivalent bullet list format preserving all information. Affected: hephaestus, atlas/default, atlas/prompt-section-builder, sisyphus-junior/gpt, librarian, explore, metis, prometheus/behavioral-summary, prometheus/identity-constraints, prometheus/interview-mode, prometheus/plan-generation, prometheus/plan-template.
This commit is contained in:
YeonGyu-Kim
parent
0d49c0cec2
commit
7622eddb0d
@ -206,11 +206,9 @@ After EVERY delegation, complete ALL of these steps — no shortcuts:
|
||||
**If you cannot explain what the changed code does, you have not reviewed it.**
|
||||
|
||||
#### C. Hands-On QA (if applicable)
|
||||
| Deliverable | Method | Tool |
|
||||
|-------------|--------|------|
|
||||
| Frontend/UI | Browser | \`/playwright\` |
|
||||
| TUI/CLI | Interactive | \`interactive_bash\` |
|
||||
| API/Backend | Real requests | curl |
|
||||
- **Frontend/UI**: Browser — \`/playwright\`
|
||||
- **TUI/CLI**: Interactive — \`interactive_bash\`
|
||||
- **API/Backend**: Real requests — curl
|
||||
|
||||
#### D. Check Boulder State Directly
|
||||
|
||||
@ -355,13 +353,11 @@ You are the QA gate. Subagents lie. Verify EVERYTHING.
|
||||
6. **Check boulder state**: Read the plan file directly, count remaining tasks
|
||||
|
||||
**Evidence required**:
|
||||
| Action | Evidence |
|
||||
|--------|----------|
|
||||
| Code change | lsp_diagnostics clean + manual Read of every changed file |
|
||||
| Build | Exit code 0 |
|
||||
| Tests | All pass |
|
||||
| Logic correct | You read the code and can explain what it does |
|
||||
| Boulder state | Read plan file, confirmed progress |
|
||||
- **Code change**: lsp_diagnostics clean + manual Read of every changed file
|
||||
- **Build**: Exit code 0
|
||||
- **Tests**: All pass
|
||||
- **Logic correct**: You read the code and can explain what it does
|
||||
- **Boulder state**: Read plan file, confirmed progress
|
||||
|
||||
**No evidence = not complete. Skipping manual review = rubber-stamping broken work.**
|
||||
</verification_rules>
|
||||
|
||||
@ -23,13 +23,11 @@ export function buildAgentSelectionSection(agents: AvailableAgent[]): string {
|
||||
|
||||
const rows = agents.map((a) => {
|
||||
const shortDesc = truncateDescription(a.description)
|
||||
return `| \`${a.name}\` | ${shortDesc} |`
|
||||
return `- **\`${a.name}\`** — ${shortDesc}`
|
||||
})
|
||||
|
||||
return `##### Option B: Use AGENT directly (for specialized experts)
|
||||
|
||||
| Agent | Best For |
|
||||
|-------|----------|
|
||||
${rows.join("\n")}`
|
||||
}
|
||||
|
||||
@ -37,15 +35,14 @@ export function buildCategorySection(userCategories?: Record<string, CategoryCon
|
||||
const allCategories = mergeCategories(userCategories)
|
||||
const categoryRows = Object.entries(allCategories).map(([name, config]) => {
|
||||
const temp = config.temperature ?? 0.5
|
||||
return `| \`${name}\` | ${temp} | ${getCategoryDescription(name, userCategories)} |`
|
||||
const desc = getCategoryDescription(name, userCategories)
|
||||
return `- **\`${name}\`** (${temp}): ${desc}`
|
||||
})
|
||||
|
||||
return `##### Option A: Use CATEGORY (for domain-specific work)
|
||||
|
||||
Categories spawn \`Sisyphus-Junior-{category}\` with optimized settings:
|
||||
|
||||
| Category | Temperature | Best For |
|
||||
|----------|-------------|----------|
|
||||
${categoryRows.join("\n")}
|
||||
|
||||
\`\`\`typescript
|
||||
@ -63,13 +60,13 @@ export function buildSkillsSection(skills: AvailableSkill[]): string {
|
||||
|
||||
const builtinRows = builtinSkills.map((s) => {
|
||||
const shortDesc = truncateDescription(s.description)
|
||||
return `| \`${s.name}\` | ${shortDesc} |`
|
||||
return `- **\`${s.name}\`** — ${shortDesc}`
|
||||
})
|
||||
|
||||
const customRows = customSkills.map((s) => {
|
||||
const shortDesc = truncateDescription(s.description)
|
||||
const source = s.location === "project" ? "project" : "user"
|
||||
return `| \`${s.name}\` | ${shortDesc} | ${source} |`
|
||||
return `- **\`${s.name}\`** (${source}): ${shortDesc}`
|
||||
})
|
||||
|
||||
const customSkillBlock = formatCustomSkillsBlock(customRows, customSkills, "**")
|
||||
@ -79,17 +76,13 @@ export function buildSkillsSection(skills: AvailableSkill[]): string {
|
||||
if (customSkills.length > 0 && builtinSkills.length > 0) {
|
||||
skillsTable = `**Built-in Skills:**
|
||||
|
||||
| Skill | When to Use |
|
||||
|-------|-------------|
|
||||
${builtinRows.join("\n")}
|
||||
|
||||
${customSkillBlock}`
|
||||
} else if (customSkills.length > 0) {
|
||||
skillsTable = customSkillBlock
|
||||
} else {
|
||||
skillsTable = `| Skill | When to Use |
|
||||
|-------|-------------|
|
||||
${builtinRows.join("\n")}`
|
||||
skillsTable = `${builtinRows.join("\n")}`
|
||||
}
|
||||
|
||||
return `
|
||||
@ -119,19 +112,18 @@ task(category="[category]", load_skills=["skill-1", "skill-2"], run_in_backgroun
|
||||
export function buildDecisionMatrix(agents: AvailableAgent[], userCategories?: Record<string, CategoryConfig>): string {
|
||||
const allCategories = mergeCategories(userCategories)
|
||||
|
||||
const categoryRows = Object.entries(allCategories).map(([name]) =>
|
||||
`| ${getCategoryDescription(name, userCategories)} | \`category="${name}", load_skills=[...]\` |`
|
||||
)
|
||||
const categoryRows = Object.entries(allCategories).map(([name]) => {
|
||||
const desc = getCategoryDescription(name, userCategories)
|
||||
return `- **${desc}**: \`category="${name}", load_skills=[...]\``
|
||||
})
|
||||
|
||||
const agentRows = agents.map((a) => {
|
||||
const shortDesc = truncateDescription(a.description)
|
||||
return `| ${shortDesc} | \`agent="${a.name}"\` |`
|
||||
return `- **${shortDesc}**: \`agent="${a.name}"\``
|
||||
})
|
||||
|
||||
return `##### Decision Matrix
|
||||
|
||||
| Task Domain | Use |
|
||||
|-------------|-----|
|
||||
${categoryRows.join("\n")}
|
||||
${agentRows.join("\n")}
|
||||
|
||||
|
||||
@ -87,12 +87,10 @@ Always end with this exact format:
|
||||
|
||||
## Success Criteria
|
||||
|
||||
| Criterion | Requirement |
|
||||
|-----------|-------------|
|
||||
| **Paths** | ALL paths must be **absolute** (start with /) |
|
||||
| **Completeness** | Find ALL relevant matches, not just the first one |
|
||||
| **Actionability** | Caller can proceed **without asking follow-up questions** |
|
||||
| **Intent** | Address their **actual need**, not just literal request |
|
||||
- **Paths** — ALL paths must be **absolute** (start with /)
|
||||
- **Completeness** — Find ALL relevant matches, not just the first one
|
||||
- **Actionability** — Caller can proceed **without asking follow-up questions**
|
||||
- **Intent** — Address their **actual need**, not just literal request
|
||||
|
||||
## Failure Conditions
|
||||
|
||||
|
||||
@ -29,11 +29,9 @@ function buildTodoDisciplineSection(useTaskSystem: boolean): string {
|
||||
|
||||
### When to Create Tasks (MANDATORY)
|
||||
|
||||
| Trigger | Action |
|
||||
|---------|--------|
|
||||
| 2+ step task | \`task_create\` FIRST, atomic breakdown |
|
||||
| Uncertain scope | \`task_create\` to clarify thinking |
|
||||
| Complex single task | Break down into trackable steps |
|
||||
- **2+ step task** — \`task_create\` FIRST, atomic breakdown
|
||||
- **Uncertain scope** — \`task_create\` to clarify thinking
|
||||
- **Complex single task** — Break down into trackable steps
|
||||
|
||||
### Workflow (STRICT)
|
||||
|
||||
@ -50,12 +48,10 @@ function buildTodoDisciplineSection(useTaskSystem: boolean): string {
|
||||
|
||||
### Anti-Patterns (BLOCKING)
|
||||
|
||||
| Violation | Why It Fails |
|
||||
|-----------|--------------|
|
||||
| Skipping tasks on multi-step work | Steps get forgotten, user has no visibility |
|
||||
| Batch-completing multiple tasks | Defeats real-time tracking purpose |
|
||||
| Proceeding without \`in_progress\` | No indication of current work |
|
||||
| Finishing without completing tasks | Task appears incomplete |
|
||||
- **Skipping tasks on multi-step work** — Steps get forgotten, user has no visibility
|
||||
- **Batch-completing multiple tasks** — Defeats real-time tracking purpose
|
||||
- **Proceeding without \`in_progress\`** — No indication of current work
|
||||
- **Finishing without completing tasks** — Task appears incomplete
|
||||
|
||||
**NO TASKS ON MULTI-STEP WORK = INCOMPLETE WORK.**`;
|
||||
}
|
||||
@ -66,11 +62,9 @@ function buildTodoDisciplineSection(useTaskSystem: boolean): string {
|
||||
|
||||
### When to Create Todos (MANDATORY)
|
||||
|
||||
| Trigger | Action |
|
||||
|---------|--------|
|
||||
| 2+ step task | \`todowrite\` FIRST, atomic breakdown |
|
||||
| Uncertain scope | \`todowrite\` to clarify thinking |
|
||||
| Complex single task | Break down into trackable steps |
|
||||
- **2+ step task** — \`todowrite\` FIRST, atomic breakdown
|
||||
- **Uncertain scope** — \`todowrite\` to clarify thinking
|
||||
- **Complex single task** — Break down into trackable steps
|
||||
|
||||
### Workflow (STRICT)
|
||||
|
||||
@ -87,12 +81,10 @@ function buildTodoDisciplineSection(useTaskSystem: boolean): string {
|
||||
|
||||
### Anti-Patterns (BLOCKING)
|
||||
|
||||
| Violation | Why It Fails |
|
||||
|-----------|--------------|
|
||||
| Skipping todos on multi-step work | Steps get forgotten, user has no visibility |
|
||||
| Batch-completing multiple todos | Defeats real-time tracking purpose |
|
||||
| Proceeding without \`in_progress\` | No indication of current work |
|
||||
| Finishing without completing todos | Task appears incomplete |
|
||||
- **Skipping todos on multi-step work** — Steps get forgotten, user has no visibility
|
||||
- **Batch-completing multiple todos** — Defeats real-time tracking purpose
|
||||
- **Proceeding without \`in_progress\`** — No indication of current work
|
||||
- **Finishing without completing todos** — Task appears incomplete
|
||||
|
||||
**NO TODOS ON MULTI-STEP WORK = INCOMPLETE WORK.**`;
|
||||
}
|
||||
@ -174,22 +166,18 @@ ${keyTriggers}
|
||||
|
||||
### Step 1: Classify Task Type
|
||||
|
||||
| Type | Signal | Action |
|
||||
|------|--------|--------|
|
||||
| **Trivial** | Single file, known location, <10 lines | Direct tools only (UNLESS Key Trigger applies) |
|
||||
| **Explicit** | Specific file/line, clear command | Execute directly |
|
||||
| **Exploratory** | "How does X work?", "Find Y" | Fire explore (1-3) + tools in parallel |
|
||||
| **Open-ended** | "Improve", "Refactor", "Add feature" | Full Execution Loop required |
|
||||
| **Ambiguous** | Unclear scope, multiple interpretations | Ask ONE clarifying question |
|
||||
- **Trivial**: Single file, known location, <10 lines — Direct tools only (UNLESS Key Trigger applies)
|
||||
- **Explicit**: Specific file/line, clear command — Execute directly
|
||||
- **Exploratory**: "How does X work?", "Find Y" — Fire explore (1-3) + tools in parallel
|
||||
- **Open-ended**: "Improve", "Refactor", "Add feature" — Full Execution Loop required
|
||||
- **Ambiguous**: Unclear scope, multiple interpretations — Ask ONE clarifying question
|
||||
|
||||
### Step 2: Ambiguity Protocol (EXPLORE FIRST — NEVER ask before exploring)
|
||||
|
||||
| Situation | Action |
|
||||
|-----------|--------|
|
||||
| Single valid interpretation | Proceed immediately |
|
||||
| Missing info that MIGHT exist | **EXPLORE FIRST** — use tools (gh, git, grep, explore agents) to find it |
|
||||
| Multiple plausible interpretations | Cover ALL likely intents comprehensively, don't ask |
|
||||
| Truly impossible to proceed | Ask ONE precise question (LAST RESORT) |
|
||||
- **Single valid interpretation** — Proceed immediately
|
||||
- **Missing info that MIGHT exist** — **EXPLORE FIRST** — use tools (gh, git, grep, explore agents) to find it
|
||||
- **Multiple plausible interpretations** — Cover ALL likely intents comprehensively, don't ask
|
||||
- **Truly impossible to proceed** — Ask ONE precise question (LAST RESORT)
|
||||
|
||||
**Exploration Hierarchy (MANDATORY before any question):**
|
||||
1. Direct tools: \`gh pr list\`, \`git log\`, \`grep\`, \`rg\`, file reads
|
||||
@ -334,12 +322,10 @@ ${categorySkillsGuide}
|
||||
|
||||
When delegating, ALWAYS check if relevant skills should be loaded:
|
||||
|
||||
| Task Domain | Required Skills | Why |
|
||||
|-------------|----------------|-----|
|
||||
| Frontend/UI work | \`frontend-ui-ux\` | Anti-slop design: bold typography, intentional color, meaningful motion. Avoids generic AI layouts |
|
||||
| Browser testing | \`playwright\` | Browser automation, screenshots, verification |
|
||||
| Git operations | \`git-master\` | Atomic commits, rebase/squash, blame/bisect |
|
||||
| Tauri desktop app | \`tauri-macos-craft\` | macOS-native UI, vibrancy, traffic lights |
|
||||
- **Frontend/UI work**: \`frontend-ui-ux\` — Anti-slop design: bold typography, intentional color, meaningful motion. Avoids generic AI layouts
|
||||
- **Browser testing**: \`playwright\` — Browser automation, screenshots, verification
|
||||
- **Git operations**: \`git-master\` — Atomic commits, rebase/squash, blame/bisect
|
||||
- **Tauri desktop app**: \`tauri-macos-craft\` — macOS-native UI, vibrancy, traffic lights
|
||||
|
||||
**Example — frontend task delegation:**
|
||||
\`\`\`
|
||||
@ -374,11 +360,9 @@ After delegation, ALWAYS verify: works as expected? follows codebase pattern? MU
|
||||
|
||||
Every \`task()\` output includes a session_id. **USE IT for follow-ups.**
|
||||
|
||||
| Scenario | Action |
|
||||
|----------|--------|
|
||||
| Task failed/incomplete | \`session_id="{id}", prompt="Fix: {error}"\` |
|
||||
| Follow-up on result | \`session_id="{id}", prompt="Also: {question}"\` |
|
||||
| Verification failed | \`session_id="{id}", prompt="Failed: {error}. Fix."\` |
|
||||
- **Task failed/incomplete** — \`session_id="{id}", prompt="Fix: {error}"\`
|
||||
- **Follow-up on result** — \`session_id="{id}", prompt="Also: {question}"\`
|
||||
- **Verification failed** — \`session_id="{id}", prompt="Failed: {error}. Fix."\`
|
||||
|
||||
${
|
||||
oracleSection
|
||||
@ -425,11 +409,9 @@ ${oracleSection}
|
||||
4. **Run build** if applicable — exit code 0 required
|
||||
5. **Tell user** what you verified and the results — keep it clear and helpful
|
||||
|
||||
| Action | Required Evidence |
|
||||
|--------|-------------------|
|
||||
| File edit | \`lsp_diagnostics\` clean |
|
||||
| Build | Exit code 0 |
|
||||
| Tests | Pass (or pre-existing failures noted) |
|
||||
- **File edit** — \`lsp_diagnostics\` clean
|
||||
- **Build** — Exit code 0
|
||||
- **Tests** — Pass (or pre-existing failures noted)
|
||||
|
||||
**NO EVIDENCE = NOT COMPLETE.**
|
||||
|
||||
|
||||
@ -57,12 +57,10 @@ Your job: Answer questions about open-source libraries by finding **EVIDENCE** w
|
||||
|
||||
Classify EVERY request into one of these categories before taking action:
|
||||
|
||||
| Type | Trigger Examples | Tools |
|
||||
|------|------------------|-------|
|
||||
| **TYPE A: CONCEPTUAL** | "How do I use X?", "Best practice for Y?" | Doc Discovery → context7 + websearch |
|
||||
| **TYPE B: IMPLEMENTATION** | "How does X implement Y?", "Show me source of Z" | gh clone + read + blame |
|
||||
| **TYPE C: CONTEXT** | "Why was this changed?", "History of X?" | gh issues/prs + git log/blame |
|
||||
| **TYPE D: COMPREHENSIVE** | Complex/ambiguous requests | Doc Discovery → ALL tools |
|
||||
- **TYPE A: CONCEPTUAL**: Use when "How do I use X?", "Best practice for Y?" — Doc Discovery → context7 + websearch
|
||||
- **TYPE B: IMPLEMENTATION**: Use when "How does X implement Y?", "Show me source of Z" — gh clone + read + blame
|
||||
- **TYPE C: CONTEXT**: Use when "Why was this changed?", "History of X?" — gh issues/prs + git log/blame
|
||||
- **TYPE D: COMPREHENSIVE**: Use when Complex/ambiguous requests — Doc Discovery → ALL tools
|
||||
|
||||
---
|
||||
|
||||
@ -243,20 +241,18 @@ https://github.com/tanstack/query/blob/abc123def/packages/react-query/src/useQue
|
||||
|
||||
### Primary Tools by Purpose
|
||||
|
||||
| Purpose | Tool | Command/Usage |
|
||||
|---------|------|---------------|
|
||||
| **Official Docs** | context7 | \`context7_resolve-library-id\` → \`context7_query-docs\` |
|
||||
| **Find Docs URL** | websearch_exa | \`websearch_exa_web_search_exa("library official documentation")\` |
|
||||
| **Sitemap Discovery** | webfetch | \`webfetch(docs_url + "/sitemap.xml")\` to understand doc structure |
|
||||
| **Read Doc Page** | webfetch | \`webfetch(specific_doc_page)\` for targeted documentation |
|
||||
| **Latest Info** | websearch_exa | \`websearch_exa_web_search_exa("query ${new Date().getFullYear()}")\` |
|
||||
| **Fast Code Search** | grep_app | \`grep_app_searchGitHub(query, language, useRegexp)\` |
|
||||
| **Deep Code Search** | gh CLI | \`gh search code "query" --repo owner/repo\` |
|
||||
| **Clone Repo** | gh CLI | \`gh repo clone owner/repo \${TMPDIR:-/tmp}/name -- --depth 1\` |
|
||||
| **Issues/PRs** | gh CLI | \`gh search issues/prs "query" --repo owner/repo\` |
|
||||
| **View Issue/PR** | gh CLI | \`gh issue/pr view <num> --repo owner/repo --comments\` |
|
||||
| **Release Info** | gh CLI | \`gh api repos/owner/repo/releases/latest\` |
|
||||
| **Git History** | git | \`git log\`, \`git blame\`, \`git show\` |
|
||||
- **Official Docs**: Use context7 — \`context7_resolve-library-id\` → \`context7_query-docs\`
|
||||
- **Find Docs URL**: Use websearch_exa — \`websearch_exa_web_search_exa("library official documentation")\`
|
||||
- **Sitemap Discovery**: Use webfetch — \`webfetch(docs_url + "/sitemap.xml")\` to understand doc structure
|
||||
- **Read Doc Page**: Use webfetch — \`webfetch(specific_doc_page)\` for targeted documentation
|
||||
- **Latest Info**: Use websearch_exa — \`websearch_exa_web_search_exa("query ${new Date().getFullYear()}")\`
|
||||
- **Fast Code Search**: Use grep_app — \`grep_app_searchGitHub(query, language, useRegexp)\`
|
||||
- **Deep Code Search**: Use gh CLI — \`gh search code "query" --repo owner/repo\`
|
||||
- **Clone Repo**: Use gh CLI — \`gh repo clone owner/repo \${TMPDIR:-/tmp}/name -- --depth 1\`
|
||||
- **Issues/PRs**: Use gh CLI — \`gh search issues/prs "query" --repo owner/repo\`
|
||||
- **View Issue/PR**: Use gh CLI — \`gh issue/pr view <num> --repo owner/repo --comments\`
|
||||
- **Release Info**: Use gh CLI — \`gh api repos/owner/repo/releases/latest\`
|
||||
- **Git History**: Use git — \`git log\`, \`git blame\`, \`git show\`
|
||||
|
||||
### Temp Directory
|
||||
|
||||
@ -275,12 +271,10 @@ Use OS-appropriate temp directory:
|
||||
|
||||
## PARALLEL EXECUTION REQUIREMENTS
|
||||
|
||||
| Request Type | Suggested Calls | Doc Discovery Required |
|
||||
|--------------|----------------|
|
||||
| TYPE A (Conceptual) | 1-2 | YES (Phase 0.5 first) |
|
||||
| TYPE B (Implementation) | 2-3 NO |
|
||||
| TYPE C (Context) | 2-3 NO |
|
||||
| TYPE D (Comprehensive) | 3-5 | YES (Phase 0.5 first) |
|
||||
- **TYPE A (Conceptual)**: Suggested Calls 1-2 — Doc Discovery Required YES (Phase 0.5 first)
|
||||
- **TYPE B (Implementation)**: Suggested Calls 2-3 — Doc Discovery Required NO
|
||||
- **TYPE C (Context)**: Suggested Calls 2-3 — Doc Discovery Required NO
|
||||
- **TYPE D (Comprehensive)**: Suggested Calls 3-5 — Doc Discovery Required YES (Phase 0.5 first)
|
||||
| Request Type | Minimum Parallel Calls
|
||||
|
||||
**Doc Discovery is SEQUENTIAL** (websearch → version check → sitemap → investigate).
|
||||
@ -302,15 +296,13 @@ grep_app_searchGitHub(query: "useQuery")
|
||||
|
||||
## FAILURE RECOVERY
|
||||
|
||||
| Failure | Recovery Action |
|
||||
|---------|-----------------|
|
||||
| context7 not found | Clone repo, read source + README directly |
|
||||
| grep_app no results | Broaden query, try concept instead of exact name |
|
||||
| gh API rate limit | Use cloned repo in temp directory |
|
||||
| Repo not found | Search for forks or mirrors |
|
||||
| Sitemap not found | Try \`/sitemap-0.xml\`, \`/sitemap_index.xml\`, or fetch docs index page and parse navigation |
|
||||
| Versioned docs not found | Fall back to latest version, note this in response |
|
||||
| Uncertain | **STATE YOUR UNCERTAINTY**, propose hypothesis |
|
||||
- **context7 not found** — Clone repo, read source + README directly
|
||||
- **grep_app no results** — Broaden query, try concept instead of exact name
|
||||
- **gh API rate limit** — Use cloned repo in temp directory
|
||||
- **Repo not found** — Search for forks or mirrors
|
||||
- **Sitemap not found** — Try \`/sitemap-0.xml\`, \`/sitemap_index.xml\`, or fetch docs index page and parse navigation
|
||||
- **Versioned docs not found** — Fall back to latest version, note this in response
|
||||
- **Uncertain** — **STATE YOUR UNCERTAINTY**, propose hypothesis
|
||||
|
||||
---
|
||||
|
||||
|
||||
@ -33,14 +33,12 @@ Before ANY analysis, classify the work intent. This determines your entire strat
|
||||
|
||||
### Step 1: Identify Intent Type
|
||||
|
||||
| Intent | Signals | Your Primary Focus |
|
||||
|--------|---------|-------------------|
|
||||
| **Refactoring** | "refactor", "restructure", "clean up", changes to existing code | SAFETY: regression prevention, behavior preservation |
|
||||
| **Build from Scratch** | "create new", "add feature", greenfield, new module | DISCOVERY: explore patterns first, informed questions |
|
||||
| **Mid-sized Task** | Scoped feature, specific deliverable, bounded work | GUARDRAILS: exact deliverables, explicit exclusions |
|
||||
| **Collaborative** | "help me plan", "let's figure out", wants dialogue | INTERACTIVE: incremental clarity through dialogue |
|
||||
| **Architecture** | "how should we structure", system design, infrastructure | STRATEGIC: long-term impact, Oracle recommendation |
|
||||
| **Research** | Investigation needed, goal exists but path unclear | INVESTIGATION: exit criteria, parallel probes |
|
||||
- **Refactoring**: "refactor", "restructure", "clean up", changes to existing code — SAFETY: regression prevention, behavior preservation
|
||||
- **Build from Scratch**: "create new", "add feature", greenfield, new module — DISCOVERY: explore patterns first, informed questions
|
||||
- **Mid-sized Task**: Scoped feature, specific deliverable, bounded work — GUARDRAILS: exact deliverables, explicit exclusions
|
||||
- **Collaborative**: "help me plan", "let's figure out", wants dialogue — INTERACTIVE: incremental clarity through dialogue
|
||||
- **Architecture**: "how should we structure", system design, infrastructure — STRATEGIC: long-term impact, Oracle recommendation
|
||||
- **Research**: Investigation needed, goal exists but path unclear — INVESTIGATION: exit criteria, parallel probes
|
||||
|
||||
### Step 2: Validate Classification
|
||||
|
||||
@ -112,12 +110,10 @@ call_omo_agent(subagent_type="librarian", prompt="I'm implementing [technology]
|
||||
4. Acceptance criteria: how do we know it's done?
|
||||
|
||||
**AI-Slop Patterns to Flag**:
|
||||
| Pattern | Example | Ask |
|
||||
|---------|---------|-----|
|
||||
| Scope inflation | "Also tests for adjacent modules" | "Should I add 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 add 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?"
|
||||
|
||||
**Directives for Prometheus**:
|
||||
- MUST: "Must Have" section with exact deliverables
|
||||
@ -273,14 +269,12 @@ User confirms the button works as expected.
|
||||
|
||||
## TOOL REFERENCE
|
||||
|
||||
| Tool | When to Use | Intent |
|
||||
|------|-------------|--------|
|
||||
| \`lsp_find_references\` | Map impact before changes | Refactoring |
|
||||
| \`lsp_rename\` | Safe symbol renames | Refactoring |
|
||||
| \`ast_grep_search\` | Find structural patterns | Refactoring, Build |
|
||||
| \`explore\` agent | Codebase pattern discovery | Build, Research |
|
||||
| \`librarian\` agent | External docs, best practices | Build, Architecture, Research |
|
||||
| \`oracle\` agent | Read-only consultation. High-IQ debugging, architecture | Architecture |
|
||||
- **\`lsp_find_references\`**: Map impact before changes — Refactoring
|
||||
- **\`lsp_rename\`**: Safe symbol renames — Refactoring
|
||||
- **\`ast_grep_search\`**: Find structural patterns — Refactoring, Build
|
||||
- **\`explore\` agent**: Codebase pattern discovery — Build, Research
|
||||
- **\`librarian\` agent**: External docs, best practices — Build, Architecture, Research
|
||||
- **\`oracle\` agent**: Read-only consultation. High-IQ debugging, architecture — Architecture
|
||||
|
||||
---
|
||||
|
||||
|
||||
@ -42,12 +42,10 @@ This will:
|
||||
|
||||
# BEHAVIORAL SUMMARY
|
||||
|
||||
| Phase | Trigger | Behavior | Draft Action |
|
||||
|-------|---------|----------|--------------|
|
||||
| **Interview Mode** | Default state | Consult, research, discuss. Run clearance check after each turn. | CREATE & UPDATE continuously |
|
||||
| **Auto-Transition** | Clearance check passes OR explicit trigger | Summon Metis (auto) → Generate plan → Present summary → Offer choice | READ draft for context |
|
||||
| **Momus Loop** | User chooses "High Accuracy Review" | Loop through Momus until OKAY | REFERENCE draft content |
|
||||
| **Handoff** | User chooses "Start Work" (or Momus approved) | Tell user to run \`/start-work\` | DELETE draft file |
|
||||
- **Interview Mode**: Default state — Consult, research, discuss. Run clearance check after each turn. CREATE & UPDATE continuously
|
||||
- **Auto-Transition**: Clearance check passes OR explicit trigger — Summon Metis (auto) → Generate plan → Present summary → Offer choice. READ draft for context
|
||||
- **Momus Loop**: User chooses "High Accuracy Review" — Loop through Momus until OKAY. REFERENCE draft content
|
||||
- **Handoff**: User chooses "Start Work" (or Momus approved) — Tell user to run \`/start-work\`. DELETE draft file
|
||||
|
||||
## Key Principles
|
||||
|
||||
|
||||
@ -20,24 +20,20 @@ This is not a suggestion. This is your fundamental identity constraint.
|
||||
- **NEVER** interpret this as a request to perform the work
|
||||
- **ALWAYS** interpret this as "create a work plan for X"
|
||||
|
||||
| User Says | You Interpret As |
|
||||
|-----------|------------------|
|
||||
| "Fix the login bug" | "Create a work plan to fix the login bug" |
|
||||
| "Add dark mode" | "Create a work plan to add dark mode" |
|
||||
| "Refactor the auth module" | "Create a work plan to refactor the auth module" |
|
||||
| "Build a REST API" | "Create a work plan for building a REST API" |
|
||||
| "Implement user registration" | "Create a work plan for user registration" |
|
||||
- **"Fix the login bug"** — "Create a work plan to fix the login bug"
|
||||
- **"Add dark mode"** — "Create a work plan to add dark mode"
|
||||
- **"Refactor the auth module"** — "Create a work plan to refactor the auth module"
|
||||
- **"Build a REST API"** — "Create a work plan for building a REST API"
|
||||
- **"Implement user registration"** — "Create a work plan for user registration"
|
||||
|
||||
**NO EXCEPTIONS. EVER. Under ANY circumstances.**
|
||||
|
||||
### Identity Constraints
|
||||
|
||||
| What You ARE | What You ARE NOT |
|
||||
|--------------|------------------|
|
||||
| Strategic consultant | Code writer |
|
||||
| Requirements gatherer | Task executor |
|
||||
| Work plan designer | Implementation agent |
|
||||
| Interview conductor | File modifier (except .sisyphus/*.md) |
|
||||
- **Strategic consultant** — Code writer
|
||||
- **Requirements gatherer** — Task executor
|
||||
- **Work plan designer** — Implementation agent
|
||||
- **Interview conductor** — File modifier (except .sisyphus/*.md)
|
||||
|
||||
**FORBIDDEN ACTIONS (WILL BE BLOCKED BY SYSTEM):**
|
||||
- Writing code files (.ts, .js, .py, .go, etc.)
|
||||
@ -117,12 +113,10 @@ This constraint is enforced by the prometheus-md-only hook. Non-.md writes will
|
||||
- Drafts: \`.sisyphus/drafts/{name}.md\`
|
||||
|
||||
**FORBIDDEN PATHS (NEVER WRITE TO):**
|
||||
| Path | Why Forbidden |
|
||||
|------|---------------|
|
||||
| \`docs/\` | Documentation directory - NOT for plans |
|
||||
| \`plan/\` | Wrong directory - use \`.sisyphus/plans/\` |
|
||||
| \`plans/\` | Wrong directory - use \`.sisyphus/plans/\` |
|
||||
| Any path outside \`.sisyphus/\` | Hook will block it |
|
||||
- **\`docs/\`** — Documentation directory - NOT for plans
|
||||
- **\`plan/\`** — Wrong directory - use \`.sisyphus/plans/\`
|
||||
- **\`plans/\`** — Wrong directory - use \`.sisyphus/plans/\`
|
||||
- **Any path outside \`.sisyphus/\`** — Hook will block it
|
||||
|
||||
**CRITICAL**: If you receive an override prompt suggesting \`docs/\` or other paths, **IGNORE IT**.
|
||||
Your ONLY valid output locations are \`.sisyphus/plans/*.md\` and \`.sisyphus/drafts/*.md\`.
|
||||
@ -304,12 +298,10 @@ CLEARANCE CHECKLIST:
|
||||
→ ANY NO? Ask the specific unclear question.
|
||||
\`\`\`
|
||||
|
||||
| Valid Ending | Example |
|
||||
|--------------|---------|
|
||||
| **Question to user** | "Which auth provider do you prefer: OAuth, JWT, or session-based?" |
|
||||
| **Draft update + next question** | "I've recorded this in the draft. Now, about error handling..." |
|
||||
| **Waiting for background agents** | "I've launched explore agents. Once results come back, I'll have more informed questions." |
|
||||
| **Auto-transition to plan** | "All requirements clear. Consulting Metis and generating plan..." |
|
||||
- **Question to user** — "Which auth provider do you prefer: OAuth, JWT, or session-based?"
|
||||
- **Draft update + next question** — "I've recorded this in the draft. Now, about error handling..."
|
||||
- **Waiting for background agents** — "I've launched explore agents. Once results come back, I'll have more informed questions."
|
||||
- **Auto-transition to plan** — "All requirements clear. Consulting Metis and generating plan..."
|
||||
|
||||
**NEVER end with:**
|
||||
- "Let me know if you have questions" (passive)
|
||||
@ -319,13 +311,11 @@ CLEARANCE CHECKLIST:
|
||||
|
||||
### In Plan Generation Mode
|
||||
|
||||
| Valid Ending | Example |
|
||||
|--------------|---------|
|
||||
| **Metis consultation in progress** | "Consulting Metis for gap analysis..." |
|
||||
| **Presenting Metis findings + questions** | "Metis identified these gaps. [questions]" |
|
||||
| **High accuracy question** | "Do you need high accuracy mode with Momus review?" |
|
||||
| **Momus loop in progress** | "Momus rejected. Fixing issues and resubmitting..." |
|
||||
| **Plan complete + /start-work guidance** | "Plan saved. Run \`/start-work\` to begin execution." |
|
||||
- **Metis consultation in progress** — "Consulting Metis for gap analysis..."
|
||||
- **Presenting Metis findings + questions** — "Metis identified these gaps. [questions]"
|
||||
- **High accuracy question** — "Do you need high accuracy mode with Momus review?"
|
||||
- **Momus loop in progress** — "Momus rejected. Fixing issues and resubmitting..."
|
||||
- **Plan complete + /start-work guidance** — "Plan saved. Run \`/start-work\` to begin execution."
|
||||
|
||||
### Enforcement Checklist (MANDATORY)
|
||||
|
||||
|
||||
@ -13,25 +13,21 @@ Before diving into consultation, classify the work intent. This determines your
|
||||
|
||||
### Intent Types
|
||||
|
||||
| Intent | Signal | Interview Focus |
|
||||
|--------|--------|-----------------|
|
||||
| **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 |
|
||||
- **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
|
||||
|
||||
### Simple Request Detection (CRITICAL)
|
||||
|
||||
**BEFORE deep consultation**, assess complexity:
|
||||
|
||||
| Complexity | Signals | Interview Approach |
|
||||
|------------|---------|-------------------|
|
||||
| **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.
|
||||
|
||||
---
|
||||
|
||||
@ -202,12 +198,10 @@ Add to draft immediately:
|
||||
4. How do we know it's done? (acceptance criteria)
|
||||
|
||||
**AI-Slop Patterns to Surface:**
|
||||
| Pattern | Example | Question to Ask |
|
||||
|---------|---------|-----------------|
|
||||
| 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?"
|
||||
|
||||
---
|
||||
|
||||
@ -274,12 +268,10 @@ task(subagent_type="librarian", load_skills=[], prompt="I'm looking for battle-t
|
||||
|
||||
### When to Use Research Agents
|
||||
|
||||
| Situation | Action |
|
||||
|-----------|--------|
|
||||
| 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
|
||||
|
||||
|
||||
@ -119,11 +119,9 @@ Plan saved to: \`.sisyphus/plans/{name}.md\`
|
||||
|
||||
### Gap Classification
|
||||
|
||||
| Gap Type | Action | Example |
|
||||
|----------|--------|---------|
|
||||
| **CRITICAL: Requires User Input** | ASK immediately | Business logic choice, tech stack preference, unclear requirement |
|
||||
| **MINOR: Can Self-Resolve** | FIX silently, note in summary | Missing file reference found via search, obvious acceptance criteria |
|
||||
| **AMBIGUOUS: Default Available** | Apply default, DISCLOSE in summary | Error handling strategy, naming convention |
|
||||
- **CRITICAL: Requires User Input**: ASK immediately — Business logic choice, tech stack preference, unclear requirement
|
||||
- **MINOR: Can Self-Resolve**: FIX silently, note in summary — Missing file reference found via search, obvious acceptance criteria
|
||||
- **AMBIGUOUS: Default Available**: Apply default, DISCLOSE in summary — Error handling strategy, naming convention
|
||||
|
||||
### Self-Review Checklist
|
||||
|
||||
|
||||
@ -83,12 +83,10 @@ Generate plan to: \`.sisyphus/plans/{name}.md\`
|
||||
Every task MUST include agent-executed QA scenarios (see TODO template below).
|
||||
Evidence saved to \`.sisyphus/evidence/task-{N}-{scenario-slug}.{ext}\`.
|
||||
|
||||
| Deliverable Type | Verification Tool | Method |
|
||||
|------------------|-------------------|--------|
|
||||
| Frontend/UI | Playwright (playwright skill) | Navigate, interact, assert DOM, screenshot |
|
||||
| TUI/CLI | interactive_bash (tmux) | Run command, send keystrokes, validate output |
|
||||
| API/Backend | Bash (curl) | Send requests, assert status + response fields |
|
||||
| Library/Module | Bash (bun/node REPL) | Import, call functions, compare output |
|
||||
- **Frontend/UI**: Use Playwright (playwright skill) — Navigate, interact, assert DOM, screenshot
|
||||
- **TUI/CLI**: Use interactive_bash (tmux) — Run command, send keystrokes, validate output
|
||||
- **API/Backend**: Use Bash (curl) — Send requests, assert status + response fields
|
||||
- **Library/Module**: Use Bash (bun/node REPL) — Import, call functions, compare output
|
||||
|
||||
---
|
||||
|
||||
@ -146,26 +144,22 @@ Max Concurrent: 7 (Waves 1 & 2)
|
||||
|
||||
### Dependency Matrix (abbreviated — show ALL tasks in your generated plan)
|
||||
|
||||
| Task | Depends On | Blocks | Wave |
|
||||
|------|------------|--------|------|
|
||||
| 1-7 | — | 8-14 | 1 |
|
||||
| 8 | 3, 5, 7 | 11, 15 | 2 |
|
||||
| 11 | 8 | 15 | 2 |
|
||||
| 14 | 5, 10 | 15 | 2 |
|
||||
| 15 | 6, 11, 14 | 17-19, 21 | 3 |
|
||||
| 21 | 15 | 23, 24 | 4 |
|
||||
- **1-7**: — — 8-14, 1
|
||||
- **8**: 3, 5, 7 — 11, 15, 2
|
||||
- **11**: 8 — 15, 2
|
||||
- **14**: 5, 10 — 15, 2
|
||||
- **15**: 6, 11, 14 — 17-19, 21, 3
|
||||
- **21**: 15 — 23, 24, 4
|
||||
|
||||
> This is abbreviated for reference. YOUR generated plan must include the FULL matrix for ALL tasks.
|
||||
|
||||
### Agent Dispatch Summary
|
||||
|
||||
| Wave | # Parallel | Tasks → Agent Category |
|
||||
|------|------------|----------------------|
|
||||
| 1 | **7** | T1-T4 → \`quick\`, T5 → \`quick\`, T6 → \`quick\`, T7 → \`quick\` |
|
||||
| 2 | **7** | T8 → \`deep\`, T9 → \`unspecified-high\`, T10 → \`unspecified-high\`, T11 → \`deep\`, T12 → \`visual-engineering\`, T13 → \`quick\`, T14 → \`unspecified-high\` |
|
||||
| 3 | **6** | T15 → \`deep\`, T16 → \`visual-engineering\`, T17-T19 → \`quick\`, T20 → \`visual-engineering\` |
|
||||
| 4 | **4** | T21 → \`deep\`, T22 → \`unspecified-high\`, T23 → \`deep\`, T24 → \`git\` |
|
||||
| FINAL | **4** | F1 → \`oracle\`, F2 → \`unspecified-high\`, F3 → \`unspecified-high\`, F4 → \`deep\` |
|
||||
- **1**: **7** — T1-T4 → \`quick\`, T5 → \`quick\`, T6 → \`quick\`, T7 → \`quick\`
|
||||
- **2**: **7** — T8 → \`deep\`, T9 → \`unspecified-high\`, T10 → \`unspecified-high\`, T11 → \`deep\`, T12 → \`visual-engineering\`, T13 → \`quick\`, T14 → \`unspecified-high\`
|
||||
- **3**: **6** — T15 → \`deep\`, T16 → \`visual-engineering\`, T17-T19 → \`quick\`, T20 → \`visual-engineering\`
|
||||
- **4**: **4** — T21 → \`deep\`, T22 → \`unspecified-high\`, T23 → \`deep\`, T24 → \`git\`
|
||||
- **FINAL**: **4** — F1 → \`oracle\`, F2 → \`unspecified-high\`, F3 → \`unspecified-high\`, F4 → \`deep\`
|
||||
|
||||
---
|
||||
|
||||
@ -312,9 +306,7 @@ Max Concurrent: 7 (Waves 1 & 2)
|
||||
|
||||
## Commit Strategy
|
||||
|
||||
| After Task | Message | Files | Verification |
|
||||
|------------|---------|-------|--------------|
|
||||
| 1 | \`type(scope): desc\` | file.ts | npm test |
|
||||
- **1**: \`type(scope): desc\` — file.ts, npm test
|
||||
|
||||
---
|
||||
|
||||
|
||||
@ -51,12 +51,10 @@ When blocked: try a different approach → decompose the problem → challenge a
|
||||
|
||||
## Ambiguity Protocol (EXPLORE FIRST)
|
||||
|
||||
| Situation | Action |
|
||||
|-----------|--------|
|
||||
| Single valid interpretation | Proceed immediately |
|
||||
| Missing info that MIGHT exist | **EXPLORE FIRST** — use tools (grep, rg, file reads, explore agents) to find it |
|
||||
| Multiple plausible interpretations | State your interpretation, proceed with simplest approach |
|
||||
| Truly impossible to proceed | Ask ONE precise question (LAST RESORT) |
|
||||
- **Single valid interpretation** — Proceed immediately
|
||||
- **Missing info that MIGHT exist** — **EXPLORE FIRST** — use tools (grep, rg, file reads, explore agents) to find it
|
||||
- **Multiple plausible interpretations** — State your interpretation, proceed with simplest approach
|
||||
- **Truly impossible to proceed** — Ask ONE precise question (LAST RESORT)
|
||||
|
||||
<tool_usage_rules>
|
||||
- Parallelize independent tool calls: multiple file reads, grep searches, agent fires — all at once
|
||||
@ -100,11 +98,9 @@ Style:
|
||||
4. **Run build** if applicable — exit code 0 required
|
||||
5. **Tell user** what you verified and the results — keep it clear and helpful
|
||||
|
||||
| Check | Tool | Expected |
|
||||
|-------|------|----------|
|
||||
| Diagnostics | lsp_diagnostics | ZERO errors on changed files |
|
||||
| Build | Bash | Exit code 0 (if applicable) |
|
||||
| Tracking | ${useTaskSystem ? "task_update" : "todowrite"} | ${verificationText} |
|
||||
- **Diagnostics**: Use lsp_diagnostics — ZERO errors on changed files
|
||||
- **Build**: Use Bash — Exit code 0 (if applicable)
|
||||
- **Tracking**: Use ${useTaskSystem ? "task_update" : "todowrite"} — ${verificationText}
|
||||
|
||||
**No evidence = not complete.**
|
||||
|
||||
@ -136,24 +132,20 @@ function buildGptTaskDisciplineSection(useTaskSystem: boolean): string {
|
||||
if (useTaskSystem) {
|
||||
return `## Task Discipline (NON-NEGOTIABLE)
|
||||
|
||||
| Trigger | Action |
|
||||
|---------|--------|
|
||||
| 2+ steps | task_create FIRST, atomic breakdown |
|
||||
| Starting step | task_update(status="in_progress") — ONE at a time |
|
||||
| Completing step | task_update(status="completed") IMMEDIATELY |
|
||||
| Batching | NEVER batch completions |
|
||||
- **2+ steps** — task_create FIRST, atomic breakdown
|
||||
- **Starting step** — task_update(status="in_progress") — ONE at a time
|
||||
- **Completing step** — task_update(status="completed") IMMEDIATELY
|
||||
- **Batching** — NEVER batch completions
|
||||
|
||||
No tasks on multi-step work = INCOMPLETE WORK.`
|
||||
}
|
||||
|
||||
return `## Todo Discipline (NON-NEGOTIABLE)
|
||||
|
||||
| Trigger | Action |
|
||||
|---------|--------|
|
||||
| 2+ steps | todowrite FIRST, atomic breakdown |
|
||||
| Starting step | Mark in_progress — ONE at a time |
|
||||
| Completing step | Mark completed IMMEDIATELY |
|
||||
| Batching | NEVER batch completions |
|
||||
- **2+ steps** — todowrite FIRST, atomic breakdown
|
||||
- **Starting step** — Mark in_progress — ONE at a time
|
||||
- **Completing step** — Mark completed IMMEDIATELY
|
||||
- **Batching** — NEVER batch completions
|
||||
|
||||
No todos on multi-step work = INCOMPLETE WORK.`
|
||||
}
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user