Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Answer Open Question With Recommendation?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/uhappylogic-answer-open-question-with-recommendation-41b6e88d)
---
name: answer-open-question-with-recommendation
description: Record an open question's embedded recommendation as that question's answer in the named mission's requirements.md.
---
# answer-open-question-with-recommendation
Records one open question's **embedded recommendation** as its answer **inline, in the
current conversation** — never in a subagent — so the recording reasoning (which block was
resolved, what decision was folded in, what cascaded) stays in context for follow-up.
To record **every** recommendation-bearing question unattended instead, use
`/answer-all-open-questions-with-recommendation`.
## Invocation
```
/answer-open-question-with-recommendation --mission <path> <Short Title>
```
`<Short Title>` must match (case-insensitive, against the block's `id`) an existing
`<open-question>` block in `<MISSION_DIR>/open_questions.xml` that the
`/recommend-all-open-questions` sweep has already annotated with a `<recommendation>`
element. The required leading `--mission <path>` names the mission by its repo-relative
path, exactly as the definition tool printed it, trailing slash included, e.g.
`mission_user-guide/`; nothing else needs to be looked up first.
## Workflow
### 1. Find the mission
First strip the leading `--mission <path>` from the invocation text by the rule in
`~/.gemini/config/plugins/gurita/shared/resolve-mission.md`, reading only the rest as `<Short Title>`.
Follow `~/.gemini/config/plugins/gurita/shared/resolve-mission.md` to resolve `<MISSION_DIR>`. Never
use a hardcoded path. Hold `<MISSION_DIR>` — you need it for the delegated recording and
the commit.
### 2. Run the shared lift-then-delegate procedure inline
Read and follow the shared procedure at
`~/.gemini/config/plugins/gurita/shared/answer-with-recommendation-procedure.md`, carrying out every step
**yourself, in this conversation**. Pass it the `<MISSION_DIR>` from step 1 and the
`<Short Title>` from the invocation as its `MISSION_DIR` and `SHORT TITLE` inputs. That
procedure owns the lift → delegate work, composing over
`~/.gemini/config/plugins/gurita/shared/answer-procedure.md`, which owns the
locate/analyse/fold/remove/cascade recording; every read and write of `open_questions.xml`
in either is a call to the plugin's open-question tool.
Hold the one line the shared procedure's `lift` call prints, "`<option>` — `<rationale>`" —
it is the commit body below.
**Clean-stop-and-point:** if the shared procedure's `lift` call fails — the tool's `Error:`
line says no block has that id, or that the matched block carries no `<recommendation>`
element — it stops without changing anything. Print the fixed line
`Recommendation not recorded — the lift was refused.` first, then below it relay that
`Error:` line to the user and point them to run `/recommend-all-open-questions` first (so the
question gets an embedded recommendation), or to record a literal answer via
`/answer-open-question <Short Title>. <answer text>`. Commit nothing — go no further.
### 3. Commit the recommendation answer
Read and follow the shared commit procedure at
`~/.gemini/config/plugins/gurita/shared/commit-procedure.md`, running its one commit-tool command yourself as
this step's one git tool call. Supply it these three inputs, using the `<MISSION_DIR>` from
step 1:
- **PATHS** — this skill's own edits: `<MISSION_DIR>/open_questions.xml` and
`<MISSION_DIR>/requirements.md`.
- **SUBJECT** — exactly `Recommendation-answer: <Short Title>` (the answered question's
handle). This distinct subject marks an accepted recommendation: when
`/capture-mission-principle-updates` walks a mission's answer commits across all three
subjects, it reads this one as evidence about principles already in the store only, never as
a source of new principles — those come from the `Manual-answer:` and `Alternative-answer:`
override signals.
- **BODY** — the lifted recommendation: the "`<option>` — `<rationale>`" line the `lift` call
printed in step 2, verbatim — the answer that was recorded.
The commit tool runs the dirty-own-path guard, the path-scoped staging, and the commit. Its
guard also covers this skill's clean-stop case: if step 2 stopped on the `lift` call's
`Error:` line, neither file changed, so the commit tool prints its no-op line
`Nothing committed — none of the paths changed.` and nothing is staged or committed.
### 4. Report findings
On the success path — the recommendation was recorded and committed — print exactly one fixed
terse status line, carrying no identifier (no Short Title, no commit subject):
```
Answer recorded.
```
Do **not** re-narrate which question resolved or how the documents changed (the removed block,
the decision folded into `## Decisions`, the cascading resolutions). Alongside the terse line
keep only the one piece of genuinely git-absent advisory output: any new open questions the
recorded decision may have introduced — surface these but do **not** add them to the document
without user confirmation.
**No-op case:** if step 3's commit tool printed
`Nothing committed — none of the paths changed.` — nothing was committed because neither file
changed (step 2's clean stop on the `lift` call's `Error:` line) — do **not** print the terse
success line. The report is step 2's stop message, opening with its fixed line.
Then stay available: the user may now ask follow-up questions or request adjustments, with
the full recording context still in hand.