B-WUVK-sdlc-backlog-capture-detect-run-under-claude
sdlc backlog capture is the CLI head — it runs claude -p to interpret
freeform text into structured fields, then calls sdlc backlog create. When
capture is invoked from inside a Claude session, that claude -p nests a
second model doing the same interpretation the ambient model could do —
redundant and risky duplication. (Nesting models is not inherently a problem;
nesting two models that do the same job is.)
Idea: have capture detect that it’s running under Claude — e.g. an
ambient env signal like CLAUDECODE / CLAUDE_CODE_* — and auto-skip its own
claude -p step (behave like --no-llm, relying on the structured flags it was
handed). The interpretation then happens exactly once, in whichever model is
already running.
Payoff: the /sdlc:backlog-capture skill can shed its “never call capture,
never claude -p” guardrail entirely — the code self-protects against redundant
nested interpretation, so the skill prose stays succinct and positive instead of
carrying prohibitions.
Out of scope for this capture: which env signal is authoritative, and whether the auto-skip should be silent or emit a one-line notice.