skills.rest
wkentaro
wkentaroCOMMUNITY
Explore all skills by this author →
Website𝕏@wkentaro_GitHub

where-am-i

Render open task decisions as an ASCII tree with markers and ordered open questions.

Updated Aug 6, 2026
Search Tags:#decision tree#visualization#task tracking#ascii#orientation#open questions
One-click install
npx skills add https://github.com/wkentaro/skills --skill where-am-i-wkentaro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: where-am-i
Source: https://github.com/wkentaro/skills/tree/main/skills/in-progress/where-am-i
Command: npx skills add https://github.com/wkentaro/skills --skill where-am-i-wkentaro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a task branches into several pending choices, it is easy to lose track of what has been decided and what still needs an answer. This Skill renders the decision state of the current conversation as an ASCII tree so you can see where you are and what to answer next. ## Core Features & Use Cases - Decision tree rendering: Draws the task as a tree with numbered top-level decisions, Q: lines at each fork, and markers for chosen, rejected, active, and not-yet-started nodes. - Orientation marker: Marks the single active fork with a YOU ARE HERE indicator and keeps settled branches visible as collapsed one-liners. - Ordered open questions: Ends every render with a numbered list of undecided nodes referenced by their [N] tags. - Use Case: During a deployment pipeline rework with choices about runner images, caching, and rollout strategy, ask where you stand and get a tree showing the pinned image decision, the active cache-strategy fork, and the remaining rollout question. ## Quick Start Ask the assistant to show where you are in the current task and what decisions are still open.

Frequently Asked Questions about where-am-i

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

FAQPage Schema
How do I see what decisions are still open in my task?▼

Ask the assistant to show where you are or what is left to decide. It reads the conversation and draws an ASCII tree of all decision forks, then lists the undecided nodes as numbered open questions in the order they need answering.

How do I track choices made during a branching task?▼

The tree marks decided nodes with a checkmark and a short reason, rejected options as not taken, and the current fork with a YOU ARE HERE marker. Settled branches stay visible as one-line summaries so the path behind you remains clear.

Does this track git branches or working directory state?▼

No, it only covers task decisions discussed in the conversation. It does not inspect git branches, files, or the working directory, and it persists nothing between renders.

What happens if every decision is already settled?▼

The full tree is rendered with all nodes marked as chosen, followed by the line stating there are no open questions. If no decision has come up yet, it says so in one line instead of drawing a tree.

When should I not use a decision tree render?▼

Avoid it for linear tasks with no branching choices, since there is nothing to draw. It also cannot recover decisions that were never discussed in the conversation, because the conversation is the only source of truth.

Related Skills

Explore More Product & Management Skills→
deerawandeerawan
1

gsd-discuss-phase

Capture unresolved implementation decisions in a phase-numbered CONTEXT.md file.

Community
Intermediate
OpenLaborOpenLabor
4

Technical Specs

Write technical specifications covering design, rollout, and open questions.

Official
Advanced
HomericIntelligenceHomericIntelligence
18

doc-generate-adr

Generate Architecture Decision Records with standardized templates and lifecycle statuses.

Official
Basic
LadderChaosLadderChaos

coordinator

Track project decisions and changes across sessions via STATUS.md, CHANGELOG.md, and DECISIONS.md.

Community
Basic