Spec Idea
Turn an idea for INITE Brain into a well-formed GitHub issue — no code. Use when someone wants to propose, suggest or request something for Brain ("it would be great if Brain…", "can you file this idea") but not build it themselves.
Install
/plugin marketplace add inite-ai/inite-brain-serviceThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add inite-ai/inite-brain-service --skill spec-ideagit clone --depth 1 https://github.com/inite-ai/inite-brain-service.git /tmp/inite-brain-service
mkdir -p ~/.claude/skills
cp -r /tmp/inite-brain-service/.claude/skills/spec-idea ~/.claude/skills/spec-ideaPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# /spec-idea — propose an idea for INITE Brain Goal: one clear issue a maintainer can say yes or no to. No branches, no code. Speak plainly; explain any term you use. 1. **Restate** the idea in one or two sentences and ask at most 3 clarifying questions (who is it for, what would they see, how would we know it works). 2. **Check for duplicates:** `gh issue list --search "<key words>" --state all`. If one exists, offer to add a comment there instead. 3. **Locate it** using the Architecture map and Zones table in `AGENTS.md`, so the spec names the area (MCP tools, REST API, extraction, search, admin UI, connectors…) and the zone. Flag red-zone touches explicitly (schema/migrations, auth/tokens, tenancy or per-user scope, GDPR forget, conflict resolution, new feature flags, eval batteries). 4. **Draft the spec** and show it: ``` Problem / Behaviour / API-MCP-UI change / Data change / Risks / Out of scope / How we'll know it works / Zone + likely files ``` 5. **File it** after the human says yes, using the product-idea form's fields (the form labels it `idea`): ```bash gh issue create --label idea --title "<plain-language title>" --body-file <spec file> ``` or point them at <https://github.com/inite-ai/inite-brain-service/issues/new?template=product-idea.yml>. 6. Give the issue link and say what happens next: a maintainer triages it; once accepted, anyone can build it with `/contribute`.
Details
- Skill name
spec-idea- Repository
- inite-ai/inite-brain-service
- Path
.claude/skills/spec-idea/SKILL.md- License
- AGPL-3.0
- Repo updated
- 18 November 2026
FAQ
What does the Spec Idea skill do?
Turn an idea for INITE Brain into a well-formed GitHub issue — no code. Use when someone wants to propose, suggest or request something for Brain ("it would be great if Brain…", "can you file this idea") but not build it themselves.
How do I install the Spec Idea skill?
Claude Code plugin: /plugin marketplace add inite-ai/inite-brain-service. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Spec Idea popular?
It lives in inite-ai/inite-brain-service, which has 43 GitHub stars and 5 forks.
Related skills
Brain Bitemporal
43inite-ai/inite-brain-service
How to query the INITE Brain knowledge graph across time — the asOf parameter, validFrom/validUntil semantics, reading retracted facts, and the memory_diff "what changed between two cursors" surface. Use when the user's question has a temporal dimension ("on X date", "before Y", "what's new since last conversation").
Brain Conflict
43inite-ai/inite-brain-service
How to detect and resolve conflicting beliefs in the INITE Brain knowledge graph — the COMPETING fact status, get_competing_facts, detect_contradiction preflight, and the human-in-the-loop adjudication workflow. Use when the timeline shows two facts disagreeing on the same predicate, or when an agent needs to decide what to record without making the disagreement worse.
Brain MCP Setup
43inite-ai/inite-brain-service
Walk a developer through connecting a fresh MCP client (Claude Desktop, Cursor, Goose v2, Aider, Continue.dev, n8n, or a raw @modelcontextprotocol/sdk client) to the INITE Brain service. Covers obtaining an API key, the per-tenant URL shape, config snippets per client, the scope matrix for the full tool surface (up to 32 built-in tools + 2 resources), and the smoke test. Use when the user says "add brain MCP", "connect brain to Claude", "set up brain for Cursor", or names any MCP-capable client.
Using Git Worktrees
43obra/clank
Create isolated git worktrees with smart directory selection and safety verification
Finishing a Development Branch
43obra/clank
Complete feature development with structured options for merge, PR, or cleanup
Diff Intake
48amplitude/mcp-marketplace
Reads a PR or branch diff and produces a structured YAML change brief for downstream analytics instrumentation skills. Use this as the first step whenever a user shares a PR link, branch comparison, or raw diff and wants to understand what changed, what needs tracking, or how to instrument a feature. Trigger on phrases like "review this PR", "what changed in this branch", "help me instrument this diff", "check analytics coverage for this change", or any request to start the analytics review workflow.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.