Issue-creation prompts must include durable issue content or source pointer #582

New Issue

2026-07-09T11:34:25-05:00

jcwalker3 commented

2026-07-09 11:34:25 -05:00

Problem

An LLM was asked to create "the drafted issue," but the title, body, acceptance criteria, labels, and durable source pointer were not present in the active context.

The LLM correctly stopped instead of fabricating an issue.

This shows a workflow gap: issue-creation prompts must either include the complete issue content or point to a durable source of truth, such as an existing Gitea issue/comment, checked-in file, or explicit scratchpad path.

Required Rule

An LLM must not create an issue from vague references like:

"the drafted issue"
"the prepared issue"
"the issue we discussed"
"the previous draft"

unless the full content is available in the current task context or retrievable from a durable source.

Expected Behavior

When issue content is missing, the LLM must return BLOCKED + DIAGNOSE and report the exact missing fields.

Acceptance Criteria

Update issue-creation workflow docs/templates to require either:
- full title/body/acceptance criteria in the prompt, or
- a durable source pointer containing the draft.
Add a preflight check for missing issue title/body/acceptance criteria.
Add examples of valid short prompts that point to durable sources.
Add examples of invalid prompts that must block.
Ensure the LLM never fabricates issue content from stale chat memory.
Ensure the LLM returns BLOCKED + DIAGNOSE when required issue content is unavailable.

## Problem An LLM was asked to create "the drafted issue," but the title, body, acceptance criteria, labels, and durable source pointer were not present in the active context. The LLM correctly stopped instead of fabricating an issue. This shows a workflow gap: issue-creation prompts must either include the complete issue content or point to a durable source of truth, such as an existing Gitea issue/comment, checked-in file, or explicit scratchpad path. ## Required Rule An LLM must not create an issue from vague references like: * "the drafted issue" * "the prepared issue" * "the issue we discussed" * "the previous draft" unless the full content is available in the current task context or retrievable from a durable source. ## Expected Behavior When issue content is missing, the LLM must return `BLOCKED + DIAGNOSE` and report the exact missing fields. ## Acceptance Criteria * Update issue-creation workflow docs/templates to require either: * full title/body/acceptance criteria in the prompt, or * a durable source pointer containing the draft. * Add a preflight check for missing issue title/body/acceptance criteria. * Add examples of valid short prompts that point to durable sources. * Add examples of invalid prompts that must block. * Ensure the LLM never fabricates issue content from stale chat memory. * Ensure the LLM returns `BLOCKED + DIAGNOSE` when required issue content is unavailable. ## Related This supports the broader goal that short prompts should work because durable project context lives in Gitea/workflow docs, not hidden chat context.

jcwalker3 added the mcp gitea documentation workflow labels 2026-07-09 11:34:29 -05:00

jcwalker3 added the status:in-progress label 2026-07-09 11:50:04 -05:00

jcwalker3 commented

2026-07-09 11:50:05 -05:00

Issue claim heartbeat

kind: claim
issue: Issue-creation prompts must include durable issue content or source pointer (#582)
branch: feat/issue-582-issue-content-preflight
phase: claimed
profile: prgs-author
pr: none
blocker: none
next_action: create worktree and begin implementation

**Issue claim heartbeat** - kind: claim - issue: #582 - branch: feat/issue-582-issue-content-preflight - phase: claimed - profile: prgs-author - pr: none - blocker: none - next_action: create worktree and begin implementation

jcwalker3 referenced this issue from a commit

2026-07-09 12:07:58 -05:00

feat: block vague-reference issue creation with content preflight (Closes #582)

jcwalker3 referenced a pull request that will close this issue

2026-07-09 12:09:45 -05:00

feat: block vague-reference issue creation with content preflight (Closes #582) #586

jcwalker3 added status:pr-open and removed status:in-progress labels 2026-07-09 12:09:47 -05:00

jcwalker3 referenced this issue

2026-07-09 12:49:05 -05:00

Test isolation: intra-file global-state leak in review-mutation ledger fails test_unknown_profile_blocks on master #590

sysadmin referenced this issue

2026-07-09 13:06:02 -05:00