Imported from samwelmunga/jenga-npm (
.claude/skills/j-btw/SKILL.md). Install upstream withnpx skills add samwelmunga/jenga-npm --skill j-btw. Copyright stays with the author.
BTW — Capture a Mission
This skill is a literal-directory-name duplicate of skills/btw/. It exists so that /j-btw (and j.j-btw) give a guaranteed-unshadowed way to reach the same flow as /btw, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare /btw alias (Claude Code's native skill resolution is a literal-string, directory-name-based match — see docs/skill-authoring.md's "Invocation Convention").
This file is generated/synced by scripts/generate-j-alias.sh btw from skills/btw/SKILL.md — do not hand-edit it; re-run the generator instead to pick up source changes.
Instructions
-
Gather mission details — Ask the user:
- Where do you want to do this?
- What would you like to do?
- What is the goal?
-
Classify the mission — Based on the description, determine if it fits into:
- An existing story
- A new story inside an existing Epic
- A new story inside a new Epic
-
Update project documentation — Add the mission to the appropriate board files:
- New story: create a file in
project/board/stories/using../pi-plan/assets/story_template.mdas the structure. - New epic: append a new Epic object to
project/PROJECT_SUMMARY.mdusing the schema in../pi-plan/assets/epic.json. - Existing story: append the new task or acceptance criterion to the matching file in
project/board/stories/.
- New story: create a file in
-
Ask the user: "now" or "later"?
- If "now" — Produce a plan for the first story related to the mission and begin implementation.
- If "later" — Confirm the mission has been recorded and resume the previous workflow.
Examples
/btw— Start the interactive mission capture flow/btw add a dark mode toggle to the settings page— Pre-fill the "what" and jump into classification