btw
Ask a quick side question about your current work without derailing the main task. Answers from existing conversation context only — no tool calls, no file reads, single concise response. Use when you need a fast answer from what is already in this session.
- License 许可
- MIT
- 所属仓库
- open-gsd/gsd-pi
- 最近更新
- 2026-11-15
- Stars
- ★ 1.4k
- Forks
- 118
01 前言 Front Matter
- name
- btw
- description
- Ask a quick side question about your current work without derailing the main task. Answers from existing conversation context only — no tool calls, no file reads, single concise response. Use when you need a fast answer from what is already in this session.
03 SKILL.md 正文
<objective> Answer a quick side question using only what is already present in the current conversation context. Do not read files, run commands, search, or use any tools. Give a single, concise response and return focus to the main work. </objective>
<behavior> This is a side question, not a task.
- Answer only from information already in the conversation (files read, decisions made, code seen, context established)
- Do NOT use any tools — no Read, no Bash, no Grep, no Search
- If the answer requires reading something new, say so briefly and suggest the user ask as a normal prompt instead
- Keep the response short and direct — one to a few sentences unless the question genuinely needs more
- Do not summarize the main work, ask follow-up questions, or offer to do anything else
- After answering, stop — do not prompt for next steps </behavior>
<quick_start>
Parse the argument after /btw as the question. Answer it directly from context.
If no argument is provided, ask: "What did you want to know?"
If the question cannot be answered from current context (requires reading a file, running a command, or information not yet in the session), respond with: "I'd need to [read X / run Y / look up Z] to answer that — ask it as a normal prompt when you're ready." </quick_start>
<examples> Good uses of /btw:
/btw what was the name of that config file again?→ answers from files already read in session/btw which branch are we on?→ answers from git context already established/btw did we already handle the null case in that function?→ answers from code already reviewed/btw what model does this use?→ answers from code or config already in context
Not a good fit for /btw (suggest normal prompt):
- Questions requiring reading a file not yet seen
- Questions requiring running a command
- Questions needing a multi-step answer or follow-up
- Starting a new task or changing direction </examples>
04 同仓库更多 Skills
write-milestone-brief
Synthesize the current conversation into a milestone brief (PRD). Saves it as the milestone CONTEXT (`gsd_summary_save`) by default, or files a GitHub issue only with explicit user confirmation. Use when asked to "turn this into a PRD", "draft a milestone brief", "capture this context", "write it up", or when enough has been discussed to commit the plan to paper. Does not interview — it synthesizes what is already known.
write-docs
Collaborative authoring workflow for proposals, technical specs, decision docs, READMEs, ADRs, and long-form prose that must work for fresh readers. Three stages: gather context, iterate on structure, reader-test for a stranger. Use when asked to "write the docs", "draft a proposal", "write a spec", "write an RFC", "write the README", or when a doc must be understandable without this session's context.
web-quality-audit
Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
verify-before-complete
Block completion claims until verification evidence has been produced in the current message. Use before marking a task/slice/milestone complete, before creating a commit or PR, before saying "it works" or "tests pass", and any time you are about to claim work is done. The rule is: evidence before claims, always — running the verification must happen now, not "earlier in the session". Fresh output or no claim.
userinterface-wiki
UI/UX best practices for web interfaces. Use when reviewing animations, CSS, audio, typography, UX patterns, prefetching, or icon implementations. Covers 11 categories from animation principles to typography. Outputs file:line findings.