Setup Skills

Generate the <project-root>/docs folder and all 14 spec files in the project root so every danielsuguimoto/skills skill can function. Skills reference these specs by path (e.g., <project-root>/docs/git-hosts.md); without them, skills cannot locate the tools they need.

Pre-flight

1. Detect project root: git rev-parse --show-toplevel or fall back to cwd. Store as <project-root>.
2. Check existing state: List <project-root>/docs/ if it exists. Check which of the 14 expected spec files already exist.
3. Decision gate:
   • All 14 exist → ask user whether to reconfigure or abort. If abort, stop.
   • Some exist → ask user whether to regenerate all or only missing ones.
   • None exist → proceed directly to interview.
4. Discover MCP servers: Use native MCP server discovery if available. Store as <mcp-inventory>. Offer detected servers as options during the interview. Skip if unsupported.

Interview

Ask the user about each tool category using the agent's native user-prompting mechanism. Three batches. Each question offers common options plus a "None / not used" option. Include the detected MCP server as an option when relevant. Present one batch at a time. Wait for all answers before proceeding to the next batch. Record every answer as <tool-selections>.

Batch 1 — Tracking, Git, Database

Question	Header	Options
What issue/ticket tracker do you use?	Issue tracker	Trello, Linear, Jira, None
What bug/error monitoring tool do you use?	Bug tracker	Sentry, Bugsnag, Rollbar, None
What git hosting platform do you use?	Git host	GitHub, GitLab, Bitbucket, None
What database inspection tools do you use?	Database	Laravel Boost MCP, Direct SQL client, None

Batch 2 — Code, Browser, Containers

Question	Header	Options
What code navigation/LSP tool do you use?	Code navigation	Serena, Sourcegraph, None
What browser automation tool do you use?	Browser	Playwright, Aside, None
What knowledge graph tool do you use?	Knowledge graph	Graphify, None
What container CLI do you use?	Container CLI	Kool, Docker Compose, None

Batch 3 — Memory, Terminal, Workspaces, Docs, MCP

Question	Header	Options
What persistent memory provider do you use?	Memory	Serena memory, Mem0, None
What terminal token compression wrapper do you use?	Terminal	RTK, None
What isolated workspace tool do you use?	Workspaces	git worktree, None
What documentation lookup tools do you use?	Doc lookup	Context7, Tavily, None
Which MCP servers should be documented?	MCP servers	Auto-detect from <mcp-inventory>, None

For the MCP servers question: if <mcp-inventory> is non-empty, offer "Use detected servers" first. If empty, offer "None" and "Other".

Generate

Create <project-root>/docs/ if missing. For each of the 14 spec files, generate the file. If the user selected "None", write a stub: **Tool**: Not configured with a note that skills referencing this spec will use fallbacks or skip.

Each spec documents the tool's interface only — no agent behavior rules:

# <Category>

**Tool**: <tool-name or "Not configured">

## Operations

| Operation | Purpose | Inputs | Outputs |
|-----------|---------|--------|---------|
<!-- Fill in: one row per operation the tool exposes -->

## Tool Details

<!-- Fill in: MCP server name + tool names, or CLI commands, or API endpoints -->

The 14 spec files and what they cover (see danielsuguimoto/skills README for the canonical list):

File	Covers
<project-root>/docs/issue-trackers.md	Load, sync, list tickets
<project-root>/docs/bug-trackers.md	Query errors, stack traces
<project-root>/docs/mcp-servers.md	List tools, call tools, discovery protocol
<project-root>/docs/git-hosts.md	PRs, reviews, issues, branches, commits
<project-root>/docs/database-tools.md	Schema, queries, REPL operations
<project-root>/docs/code-navigation.md	Find symbols, trace references, refactor
<project-root>/docs/browser-automation.md	Snapshots, element interaction, downloads
<project-root>/docs/knowledge-graphs.md	Build, query, path, explain
<project-root>/docs/container-clis.md	Lifecycle, exec, logs, scripts
<project-root>/docs/workspace-isolation.md	Detect, create, list, remove isolated workspaces
<project-root>/docs/memory-providers.md	List, read, write, edit, delete memories
<project-root>/docs/terminal-wrappers.md	Command prefixing, output filtering
<project-root>/docs/terminal-tools.md	Non-standard terminal tools replacing usual defaults
<project-root>/docs/doc-lookup.md	Framework/library/SDK docs, search fallbacks

For <project-root>/docs/mcp-servers.md: populate a server inventory section from <mcp-inventory> if the user chose to document detected servers.

Verify and Output

Confirm all 14 spec files exist. Report summary table: spec file, tool, configured or not. List files with <!-- Fill in: ... --> markers needing manual completion. Do not commit or push.