From 037fd87fe25e96cf3fbd7878c245ac3c51025185 Mon Sep 17 00:00:00 2001 From: lauren Date: Sat, 17 Oct 2026 22:41:28 -0700 Subject: [PATCH] fix(pstack): say outright that ketchup never cuts items to stay under a word count The old sentence said not to shrink items to fit. Name cutting items as well, and the word count they must not be cut to meet. --- harness/pstack/claude-code/skills/ketchup/SKILL.md | 2 +- pstack/skills/ketchup/SKILL.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/harness/pstack/claude-code/skills/ketchup/SKILL.md b/harness/pstack/claude-code/skills/ketchup/SKILL.md index 4224634e1..9eef27f92 100644 --- a/harness/pstack/claude-code/skills/ketchup/SKILL.md +++ b/harness/pstack/claude-code/skills/ketchup/SKILL.md @@ -20,7 +20,7 @@ One call can cover many items, such as each PR in a set awaiting merge. For each ## Write the reply -Spend words on the calls, not on the story. Keep what happened under 100 words, not counting pictures, and shorter when less happened. Leave out work that changed nothing for the user. Give each item about 30 words. The reply grows with the number of items: two items need well under 150 words in all, not counting pictures, and thirty need far more. Never shrink items to fit: no count in place of a list, and no link in place of an item. A link can add depth, but the reply alone must be enough to decide. +Spend words on the calls, not on the story. Keep what happened under 100 words, not counting pictures, and shorter when less happened. Leave out work that changed nothing for the user. Give each item about 30 words. The reply grows with the number of items: two items need well under 150 words in all, not counting pictures, and thirty need far more. Never cut items or shrink them to stay under a word count: no count in place of a list, and no link in place of an item. A link can add depth, but the reply alone must be enough to decide. Open with one short sentence that names what waits on the user, or says nothing does. The action items give the detail. If nothing happened and nothing waits on the user, say so and stop. diff --git a/pstack/skills/ketchup/SKILL.md b/pstack/skills/ketchup/SKILL.md index 4224634e1..9eef27f92 100644 --- a/pstack/skills/ketchup/SKILL.md +++ b/pstack/skills/ketchup/SKILL.md @@ -20,7 +20,7 @@ One call can cover many items, such as each PR in a set awaiting merge. For each ## Write the reply -Spend words on the calls, not on the story. Keep what happened under 100 words, not counting pictures, and shorter when less happened. Leave out work that changed nothing for the user. Give each item about 30 words. The reply grows with the number of items: two items need well under 150 words in all, not counting pictures, and thirty need far more. Never shrink items to fit: no count in place of a list, and no link in place of an item. A link can add depth, but the reply alone must be enough to decide. +Spend words on the calls, not on the story. Keep what happened under 100 words, not counting pictures, and shorter when less happened. Leave out work that changed nothing for the user. Give each item about 30 words. The reply grows with the number of items: two items need well under 150 words in all, not counting pictures, and thirty need far more. Never cut items or shrink them to stay under a word count: no count in place of a list, and no link in place of an item. A link can add depth, but the reply alone must be enough to decide. Open with one short sentence that names what waits on the user, or says nothing does. The action items give the detail. If nothing happened and nothing waits on the user, say so and stop.