j.btw

Captures new missions and files them into Epic and Story board structures.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/samwelmunga/jenga-npm --skill j-btw-samwelmunga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: j.btw
Source: https://github.com/samwelmunga/jenga-npm/tree/main/.agents/skills/j-btw
Command: npx skills add https://github.com/samwelmunga/jenga-npm --skill j-btw-samwelmunga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Mid-session ideas and side tasks often get lost or derail the current workflow. This Skill captures a new mission (feature, change, or addition) as it comes up, classifies it into the project's Epic/Story hierarchy, and lets you decide whether to implement it now or defer it without losing context. ## Core Features & Use Cases - Mission Capture: Interactively gathers where, what, and why for a new idea, then classifies it as a task in an existing story, a new story in an existing Epic, or a new Epic. - Board Integration: Writes the mission into Markdown board files — creating story files from a template, appending Epics to PROJECT_SUMMARY.md, or adding tasks to existing stories. - Now-or-Later Handoff: After capture, choose to plan and implement immediately or record the mission and resume the previous workflow. - Use Case: While implementing a feature you realize the settings page needs a dark mode toggle — invoke the skill to record it as a new story and continue your current work uninterrupted. ## Quick Start Ask the agent to capture a new mission, for example: btw I also need to add a dark mode toggle to the settings page.

Frequently Asked Questions about j.btw

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture a new task or idea mid-session without losing context?▼

Invoke the skill with a short description, such as "btw add a dark mode toggle". It asks where, what, and why, classifies the mission into your Epic/Story structure, records it on the board, and lets you continue your previous work.

How does the skill decide where a new mission belongs on the board?▼

It classifies the mission into one of three places: a task in an existing story, a new story inside an existing Epic, or a new story inside a new Epic. New stories use the story template and new Epics are appended to PROJECT_SUMMARY.md.

What is the difference between /btw and /j-btw?▼

Both run the identical mission-capture flow. The j-btw directory is a generated polyfill alias that guarantees the command resolves even when a host tool's built-in command shadows the bare /btw name.

Can I implement a captured mission immediately instead of deferring it?▼

Yes. After recording the mission, the skill asks "now" or "later". Choosing "now" produces a plan for the first related story and begins implementation; "later" confirms the record and resumes your prior workflow.

Why should I not hand-edit the j-btw SKILL.md file?▼

The file is generated and synced from skills/btw/SKILL.md by the generate-j-alias.sh script. Manual edits are overwritten, so changes should be made in the source skill and regenerated.