
from bkit-gemini59
Capture lightweight improvement suggestions while you work and store them locally in .bkit/btw.json for later review, analysis, or promotion into PDCA planning.
BTW (By-The-Way) is a minimal, developer-focused capture tool that lets agents record improvement suggestions, observations, and ideas without interrupting flow. It persists entries to a local .bkit/btw.json file and provides commands to list, analyze, and promote suggestions into a PDCA workflow. Use it to quickly note UX, performance, docs, security, or refactor ideas as they arise.
Invoke BTW when a user says 'btw', offers a suggestion, or asks to record an idea for later. It's ideal during active development (Do phase) for collecting quick notes that will be reviewed and triaged later. Do not use it for formal bug reporting or task tracking; promote actionable items to PDCA when ready.
Works with agents that have read/write access to the project workspace and can run simple in-agent file operations (Cursor/Gemini CLI/other dev-focused agents).
BTW is a lightweight suggestion collector that stores improvement ideas in .bkit/btw.json for later review and PDCA promotion. No bundled scripts — all logic is inline in SKILL.md instructions. The skill is well-structured with clear commands (record, list, analyze, promote) and a defined storage format. Category auto-detection is described by keyword but the analyze step relies entirely on agent judgment without concrete heuristics.
Clean skill with no security concerns. Multilingual trigger support (Korean, Japanese, Chinese, Spanish, French, German, Italian) is a nice touch. Missing error handling for corrupt/missing btw.json. The promote command creates files in docs/01-plan/features/ which assumes a specific project layout.
Batch
Run PDCA workflow commands across multiple features in parallel or bulk, with progress tracking, fail-forward behavior, and retry options.
Loop (Recurring Command Runner)
Run prompts or shell commands on a recurring interval (seconds/minutes/hours) with safety limits and optional stop conditions — useful for monitoring and period
PDCA (Plan-Do-Check-Act) Workflow
Manage Plan → Design → Do → Check → Act cycles: create plan/design docs, run gap analysis, iterate fixes, and generate completion reports.