Skip to content

Prompts opencode style #837

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
harshithmullapudi wants to merge 6 commits into
base: main
Choose a base branch
from
Open

Prompts opencode style #837

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
3344bfa
fix: use consistent grammer
harshithmullapudi May 1, 2026
f61ef8b
refactor(prompts): apply opencode-style polish to base context, decis…
harshithmullapudi May 2, 2026
a8f8274
fix(prompts): restore four-cases classifier and readiness-check sub-r…
harshithmullapudi May 2, 2026
e57cfbf
refactor(prompts): reshape assembled prompt to opencode template
harshithmullapudi May 2, 2026
fabc3ec
fix(prompts): scope /help fallback and update <capabilities> anchors
harshithmullapudi May 2, 2026
597e130
refactor(prompts): wrap top-level sections in XML tags
harshithmullapudi May 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
135 changes: 0 additions & 135 deletions apps/webapp/app/lib/prompt.server.ts
View file
Open in desktop

This file was deleted.

6 changes: 3 additions & 3 deletions apps/webapp/app/services/agent/context.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -513,19 +513,19 @@ DO NOT:
`
: `
PREP RULES:
0. CHECK INPUT SHAPE FIRST. Read the task description and decide what the user gave you (see STARTING WORK > INPUT SHAPE in <capabilities>):
0. CHECK INPUT SHAPE FIRST. Read the task description and decide what the user gave you (see \`<doing_tasks>\` > Input shape in your system prompt):

- If the description is a PLAN / RUNBOOK (explicit numbered or named steps, named data sources, named tools — the user already did the planning work):
→ Treat the description AS the plan. Do NOT re-plan, do NOT propose-and-confirm, do NOT write another plan summary. Execute the steps directly.
→ If a step has a BLOCKING gap (a referenced field doesn't exist, a destination is ambiguous in a way that affects who/what gets acted on), mark Waiting and ask one blocking question at a time. Cosmetic mismatches (label drift, format choices, defaults with one obvious answer) are NOT blockers — see WHAT NOT TO ASK ABOUT.
→ When done, write the result to the description (section="Output"), send_message with results, mark Review.

- If the description is a GOAL (a desired outcome — you need to figure out the steps):
→ Apply the COMPLEXITY rules from STARTING WORK.
→ Apply the Complexity rules from \`<doing_tasks>\`.
→ If on second look the task is actually SIMPLE (one artifact: summary, profile, brief, recap, list, lookup, single send) → it should not have landed in prep. Skip planning. Do the actual work now using gather_context / take_action, write the result to the description (section="Output"), send the result via send_message, and mark the task Review. Do NOT produce a "plan" of how you'll do it.
→ If genuinely COMPLEX (multiple independent deliverables, irreversibly bulk, user explicitly said "plan/think through", or coding) → continue to step 1 below to do the planning prep flow.

1. Run the READINESS CHECK (see <capabilities>). Load the appropriate skill from <skills>:
1. Run the readiness check (see \`<readiness_check>\`). Load the appropriate skill from \`<skills>\`:
- Unclear what's needed? → load "Gather Information" skill
- Open-ended, needs shaping? → load "Brainstorm" skill
- Multi-step, needs decomposition? → load "Plan" skill
Expand Down
Loading