blg
File a backlog item in Torque. Use when something surfaces mid-session that deserves prioritized work but is out of scope right now.
- License 许可
- MIT
- 最近更新
- 2026-10-21
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- blg
- description
- File a backlog item in Torque. Use when something surfaces mid-session that deserves prioritized work but is out of scope right now.
03 SKILL.md 正文
Fast capture into Torque. Should take one exchange — this is a capture tool, not a planning exercise.
Procedure
1. Resolve the project
In order, stopping at the first that works:
- The user named a project →
torque_project_list, match on name. - Otherwise match the current working directory against each project's
repo_path, longest prefix wins. - Otherwise ask.
Never fall back to a hardcoded project id. A backlog item filed against the wrong project is worse than one extra question.
Some
repo_pathvalues in Torque point at directories that no longer exist. If a project's name clearly matches but its path doesn't resolve, use it anyway and say so in your confirmation.
2. Shape the item
- Title — imperative, specific. "Investigate PostgreSQL migration path", not "postgres".
- Body — why it matters and enough context to act on it cold. Two or three sentences.
- Tags — infer from content; always include
backlog. - Priority —
Bunless the user says otherwise.
3. Create and confirm
torque_task_create project_id=<id> title= body= tags= status=backlog
One line back:
✓ {CW-id}: {title} [{project} · {priority} · {tags}]
Backlog vs follow-up
/blg→ Torque. A real work item with priority and a lifecycle. Use when it should get scheduled./capture-followup→ Tesseract. A soft signal for a future session, no lifecycle. Use when it should surface if someone touches that area again.
Both when it's genuinely both. Neither for passing thoughts.
Do not
- Don't file vague items. "Improve error handling" with no location is noise a future session can't act on.
- Don't file what you could just do in under a minute.
- Don't turn this into planning. Capture and move on.
04 同仓库更多 Skills
tangent
Open a browser workflow when chat is the wrong shape for structured input — triaging many items with one decision, multi-question feedback, or design review. Requires the Tangent MCP server.
release
Cut a release. Use before git tag or gh release create.
push
Push work off this machine. Use before any git push.
pull-request
Open a pull request. Use before gh pr create.
end-of-session
Wrap up a work session — reconcile the git tree, commit what this session authored, review drafts, and capture durable signal. Use when the user signals the session is ending.
commit
Commit work in a tree another session may be using. Use before any git commit.