gib/Panama
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Stop writing text into the Working Feature Proof field

Browse Source 
Dragging attachments into customfield_10142 replaces whatever text is
sitting there, so the list the skill wrote was destroyed by the upload it
was describing. Naming each artifact is already the job of the Test Cases
proof cells, which reference it by filename, and step 10 tells me which
files to upload.

Only the Story rule changes. On a Bug that field carries the test-case
table rather than prose.
This commit is contained in:
Gabriel Brown
2026-09-14 14:36:54 -04:00
parent 59192143c5
commit 85160ffef2
1 changed files with 6 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
user/agents/skills/ticket/SKILL.md
+6 -7
View File
@@ -891,13 +891,12 @@ Entered only when the user has confirmed (per Phase 0) that the plan is approved
handled and what covers it. Deliver the number asked for, not more, and pick the handled and what covers it. Deliver the number asked for, not more, and pick the
ones a reviewer most benefits from. This field, not `mr.md`. ones a reviewer most benefits from. This field, not `mr.md`.
- `customfield_10261` User Story Patch Notes: the same change in user-facing words. - `customfield_10261` User Story Patch Notes: the same change in user-facing words.
- `customfield_10142` Working Feature Proof: ALWAYS fill this on a Story, never - `customfield_10142` Working Feature Proof: leave it alone. Write nothing here.
leave it empty. It renders as its own panel in the ticket's testing section, so This field is where Gib drops the proof attachments, and dragging files into it
an empty field reads as unfilled testing even when every test-table cell is replaces whatever text is sitting there, so a written list is destroyed by the
complete (this happened on KACP-23143). At minimum it lists the files staged in upload it was describing. Naming each artifact is already the job of the Test
`proof/` for Gib to attach, one line each saying what the artifact shows, plus a Cases proof cells, which reference it by filename. Step 10 tells Gib which files
pointer that per-row proof lives in the Test Cases table. A headline artifact (a to upload. Do not PUT this field on a Story.
demo capture, a before/after pair) leads the list when one exists.
**Spike** (deliverables, not code): no test or proof fields to fill. The output is **Spike** (deliverables, not code): no test or proof fields to fill. The output is
the deliverables directory, and step 10 tells Gib which files to upload where (the the deliverables directory, and step 10 tells Gib which files to upload where (the