skills/remember-access/SKILL.md
Capture or review how this project connects to external systems (GitHub, AWS, npm, SSH, etc.) so future sessions know the auth recipe. Auto-detection hook logs candidate captures to an inbox; this skill promotes them to permanent recipes in `.planning/AUTH-RECIPES.md` and optionally to user-global memory at `~/.claude/auth-recipes/`.
npx skillsauth add jnuyens/gsd-plugin gsd:remember-accessInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Two modes:
/gsd:remember-access <system-name>: manual capture. Walks you through documenting how to authenticate to a system, writes to .planning/AUTH-RECIPES.md (per-project), optionally promotes to ~/.claude/auth-recipes/<system>.md (cross-project)./gsd:remember-access --review: surface the auto-detection inbox (.planning/.pending-auth-captures.jsonl, populated by the gsd-auth-detector PostToolUse hook), let you confirm each detection and save it as a recipe.Auto-detection runs continuously: every Bash command you execute is checked against auth-shaped patterns (gh auth login, aws configure, ssh-keygen, export GITHUB_TOKEN=..., etc.). Secret-looking content is redacted before the inbox entry is written. Review at your own pace.
Privacy: the detector NEVER stores the actual secret values. It stores the SHAPE of the command (which tool, which flags) with credential payloads replaced by [REDACTED] markers. The recipe is "how to authenticate," not "what the password is."
</context>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/remember-access.md </execution_context>
<process> Execute the remember-access workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/remember-access.md. </process>tools
Initialize a new project using Documentation-Driven Development. Research, then write user-facing docs (SPEC.md) as the spec, then user validates docs, then phases derive from doc sections. Best for CLIs, libraries, SDKs, APIs, plugin systems, anything with a well-defined user-facing surface.
tools
Plan an MVP-mode phase — captures an "As a / I want to / So that" user story, runs SPIDR splitting, then delegates to plan-phase
testing
Extract decisions, lessons, patterns, and surprises from completed phase artifacts
tools
Schedule a future resume of work - e.g. '/gsd:resume-at 09:00', '/gsd:resume-at +2h', or '/gsd:resume-at 04:00 --cmd /gsd:execute-phase 9'