mosaic/stack
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

Create Forced Continuation Prompt System #137

New Issue
Closed
opened 2026-01-30 23:42:59 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-01-30 23:42:59 +00:00
Owner
Copy Link

Build deterministic prompt generation for forcing agent continuation after gate failures.

Objective: Generate explicit continuation prompts when agents claim done but gates fail.

Problem: Agents say done prematurely. Solution: Inject non-negotiable continue command.

Prompt Template System:

  • Template per gate type (build, lint, test, coverage)
  • Variables: gate name, failures list, expected vs actual
  • Examples: 509 linting errors remain - you must fix ALL before done
  • Tone: Non-negotiable, specific, actionable

Template Examples:

  • Build failure: Build failed with X errors. Fix all compilation errors before claiming done.
  • Lint failure: Linting failed: X errors, Y warnings. Project requires 0 errors, max Z warnings.
  • Test failure: X of Y tests failing. All tests must pass before done.
  • Coverage failure: Coverage is X%, required Y%. Add tests to meet threshold.

Prompt Injection:

  • Orchestrator injects prompt into agent context
  • Agent cannot negotiate or defer
  • Prompt includes specific failures list
  • Forces agent to address exact issues

Related: L-015, #134 (orchestrator), #136 (verification engine)

Acceptance Criteria:

  • Template system implemented
  • Templates for all gate types
  • Variable substitution working
  • Prompts are clear and actionable
  • Integration with orchestrator
  • Agent receives and processes forced continuation
Build deterministic prompt generation for forcing agent continuation after gate failures. Objective: Generate explicit continuation prompts when agents claim done but gates fail. Problem: Agents say done prematurely. Solution: Inject non-negotiable continue command. Prompt Template System: - Template per gate type (build, lint, test, coverage) - Variables: gate name, failures list, expected vs actual - Examples: 509 linting errors remain - you must fix ALL before done - Tone: Non-negotiable, specific, actionable Template Examples: - Build failure: Build failed with X errors. Fix all compilation errors before claiming done. - Lint failure: Linting failed: X errors, Y warnings. Project requires 0 errors, max Z warnings. - Test failure: X of Y tests failing. All tests must pass before done. - Coverage failure: Coverage is X%, required Y%. Add tests to meet threshold. Prompt Injection: - Orchestrator injects prompt into agent context - Agent cannot negotiate or defer - Prompt includes specific failures list - Forces agent to address exact issues Related: L-015, #134 (orchestrator), #136 (verification engine) Acceptance Criteria: - Template system implemented - Templates for all gate types - Variable substitution working - Prompts are clear and actionable - Integration with orchestrator - Agent receives and processes forced continuation
jason.woltje added the p0apiapi labels 2026-01-30 23:42:59 +00:00
jason.woltje added this to the M4-LLM (0.0.4) milestone 2026-01-30 23:45:33 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai
AI/LLM integration
 api
Backend/API work
 api
auth
Authentication
 database
database
Database/schema work
 devops
Docker/deployment
 docs
Documentation
 frontend
graph
knowledge-module
migration
Data migration
 orchestrator
Orchestrator service (apps/orchestrator/)
 p0
Critical priority
 p1
High priority
 p2
Medium priority
 p3
Low priority
 performance
Performance work
 phase-1
phase-2
phase-3
phase-4
phase-5
plugin
MoltBot plugin work
 search
security
Security-related
 setup
Initial setup
 testing
Testing/QA
 web
Frontend work
No Label api api p0
Milestone
No items
No Milestone M4-LLM (0.0.4)
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaic/stack#137
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?