Qnn
iblameandrew/open-deepthink
Launch a Qualitative Neural Network (QNN) — a layered, multi-epoch brainstorm of agent personas that maps divergent strategies before implementation.
Make behavior changes using this repository's lightweight spec-driven flow.
Install Spec Change
$ npx skills add gdsfactory/sax --skill spec-change -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gdsfactory/sax spec-change --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/gdsfactory/sax.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/spec-change .claude/skills/spec-change && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "spec-change" agent skill from https://github.com/gdsfactory/sax/tree/main/.agents/skills/spec-change into .claude/skills/spec-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-change", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/gdsfactory/sax/tree/main/.agents/skills/spec-changeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add gdsfactory/sax --skill spec-change -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gdsfactory/sax spec-change --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gdsfactory/sax.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/spec-change .agents/skills/spec-change && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "spec-change" agent skill from https://github.com/gdsfactory/sax/tree/main/.agents/skills/spec-change into .agents/skills/spec-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-change", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gdsfactory/sax --skill spec-change -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gdsfactory/sax spec-change --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gdsfactory/sax.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/spec-change .cursor/skills/spec-change && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "spec-change" agent skill from https://github.com/gdsfactory/sax/tree/main/.agents/skills/spec-change into .cursor/skills/spec-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-change", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/gdsfactory/sax.git --path .agents/skills/spec-change--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add gdsfactory/sax --skill spec-change -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gdsfactory/sax spec-change --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gdsfactory/sax.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/spec-change .gemini/skills/spec-change && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "spec-change" agent skill from https://github.com/gdsfactory/sax/tree/main/.agents/skills/spec-change into .gemini/skills/spec-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-change", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install gdsfactory/sax spec-changeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add gdsfactory/sax --skill spec-change -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gdsfactory/sax.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/spec-change .github/skills/spec-change && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "spec-change" agent skill from https://github.com/gdsfactory/sax/tree/main/.agents/skills/spec-change into .github/skills/spec-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-change", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gdsfactory/sax --skill spec-change -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gdsfactory/sax spec-change --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gdsfactory/sax.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/spec-change .opencode/skills/spec-change && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "spec-change" agent skill from https://github.com/gdsfactory/sax/tree/main/.agents/skills/spec-change into .opencode/skills/spec-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-change", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
spec-change- GitHub stars
- 131
- Token cost
- ~852 tokens
- SKILL.md length
- 396 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Make behavior changes using this repository's lightweight spec-driven flow.
- Works in 6 steps: Establish the change. Summarize current… → Choose the lightest record. A clear,… → Resolve material uncertainty. The user's… → …
- Adding features
- SKILL.md covers Context, Workflow and Guardrails
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Spec Change is an agent skill from gdsfactory/sax. Make behavior changes using this repository's lightweight spec-driven flow. Use when adding features, fixing behavioral bugs, or changing contracts; also use when drafting or revising a change proposal. Keeps specs, implementation, and verification aligned without mandatory approval files or branch management.
Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Spec-driven development and Deep learning. The repository describes itself as: S + Autograd + XLA :: S-parameter based frequency domain circuit simulations and optimizations using JAX. The licence is Apache-2.0.
When your agent uses it
- Adding features
- Fixing behavioral bugs
- Changing contracts
- Also use when drafting
Example prompts
- “/spec-change”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Establish the change. Summarize current behavior, requested behavior, affected
- Choose the lightest record. A clear, local change needs only a short plan in
- Resolve material uncertainty. The user's clear request authorizes its scope.
- Implement and verify in slices. Add/update relevant tests, implement the
- Reconcile the specs. Update affected baseline contracts, evidence links, open
- Close with evidence. Report changed contracts, files, commands/results, and
What it can do on your machine
Read from SKILL.md and the folder at commit 784e750. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Spec Change loads about 852 tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 396 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from gdsfactory/sax at commit 784e750, republished under its Apache-2.0 licence (© gdsfactory). 396 words, ~852 tokens.
Download SKILL.mdSave it as
.claude/skills/spec-change/SKILL.md (or your agent's skills folder).- name
- spec-change
- description
- Make behavior changes using this repository's lightweight spec-driven flow. Use when adding features, fixing behavioral bugs, or changing contracts; also use when drafting or revising a change proposal. Keeps specs, implementation, and verification aligned without mandatory approval files or branch management.
Spec-driven change
Context
From the repository root, read AGENTS.md and specs/README.md, then only the
relevant subsystem specs and source/tests. For SAX's check commands and numerical
caveats, consult specs/verification.md. Respect a user request to bypass this flow.
Paths above are repository-root paths, not relative to this skill directory. The index is also available at specs/README.md.
Workflow
- Establish the change. Summarize current behavior, requested behavior, affected contracts, and one or more concrete acceptance checks. Inspect the implementation rather than asking the user questions the repo can answer. Distinguish intended changes from baseline discrepancies and uncertain intent.
- Choose the lightest record. A clear, local change needs only a short plan in
chat. For breaking/cross-cutting work, unresolved design choices, or work spanning
sessions, write
specs/changes/<slug>.md: intent, scope/non-goals, proposed contract, verification, unresolved decisions. Create that directory only if needed. No required numbering, status tokens, or standalone plan for mechanical edits. - Resolve material uncertainty. The user's clear request authorizes its scope. Ask only when alternatives materially change public behavior, compatibility, safety, or effort. Do not treat an observed bug as an approved requirement, and do not implement proposals when the user requested only analysis/specification.
- Implement and verify in slices. Add/update relevant tests, implement the agreed behavior, and run targeted checks before broader regressions. Use explicit tolerances and asymmetric fixtures for numerical direction. Run JIT/gradient checks only where relevant. Never weaken acceptance criteria to conceal a failure.
- Reconcile the specs. Update affected baseline contracts, evidence links, open questions, and user-facing explanations in the same change. Keep unimplemented behavior clearly proposed. Mark a completed change note as implemented; retain it only if useful rationale remains. Do not replace historical baseline run results with unqualified claims that everything is verified.
- Close with evidence. Report changed contracts, files, commands/results, and any failed or unrun checks. If blocked, state the blocker and next input needed.
Show full SKILL.md (86 more words)Show less
Guardrails
- No automatic branches, commits, stashes, dependency updates, or destructive setup. Preserve unrelated working-tree changes; ask if edits overlap unsafely.
- No mandatory pause after every tiny step. Pause for decisions, surprising failures, or user-requested review boundaries, not arbitrary line counts.
- Update existing specs instead of producing duplicate contracts. A change that leaves observable behavior intact may need no spec edit; say so briefly.
- Source, tests, and prose can each be wrong. Explain disagreements before deciding
which artifact to change.
specs/open-questions.mdis not an automatic fix list.
© gdsfactory, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/spec-change of gdsfactory/sax.
Open the folder on GitHubat commit 784e750
Compare with similar skills
Spec Change next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Spec Change this skillgdsfactory/sax | 131 | — | ~852 | Automated safety check: Pass | Apache-2.0 | |
| Qnniblameandrew/open-deepthink | 151 | — | ~7.1k | Automated safety check: Pass | MIT | |
| Tapd Story PlanTencentBlueKing/bk-bcs | 840 | — | ~886 | Automated safety check: Pass | Custom licence | |
| Tapd Story TasksTencentBlueKing/bk-bcs | 840 | — | ~900 | Automated safety check: Pass | Custom licence | |
| OpenSpec Guided OnboardingFission-AI/OpenSpec | 71k | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Readyprekuter/dryforge | 410 | 1 repos | ~6.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Tapd Story Plan
TencentBlueKing/bk-bcs
迭代执行流水线开发计划阶段。基于 spec.md 调用 /speckit.plan 以测试驱动开发模式构建 开发计划、技术调研与数据模型，并在同一 subagent 内就地做文档级合规自检，产出 plan-report.md。
Tapd Story Tasks
TencentBlueKing/bk-bcs
迭代执行流水线任务生成阶段。基于 plan.md / research.md 调用 /speckit.tasks 生成全量任务， 随后调用 /speckit.analyze 验证产物合规。两段命令通过两次 subagent 隔离执行。
OpenSpec Guided Onboarding
Fission-AI/OpenSpec
Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.
Ready
prekuter/dryforge
Understand what you mean before anything is built. An agent skill from prekuter/dryforge.
Spec Driven Develop
zhu1090093659/deepseek-pp
Automates pre-development workflow for large-scale complex tasks.
More from gdsfactory/sax
Spec Check
gdsfactory/sax
Review or refresh repository specs against implementation and tests.
Related
Questions about Spec Change
What does Spec Change do?
Make behavior changes using this repository's lightweight spec-driven flow. Spec Change is an agent skill from gdsfactory/sax. Make behavior changes using this repository's lightweight spec-driven flow.
When should I use Spec Change?
Spec Change fits situations like: adding features; fixing behavioral bugs; changing contracts; also use when drafting.
How do I install Spec Change in Claude Code?
Run `npx skills add gdsfactory/sax --skill spec-change -a claude-code`. Or copy the skill folder (.agents/skills/spec-change in gdsfactory/sax) into .claude/skills/spec-change in your project. Claude Code loads it when a task matches its description.
How do I install Spec Change in Codex?
Run `npx skills add gdsfactory/sax --skill spec-change -a codex`. Or copy the skill folder (.agents/skills/spec-change in gdsfactory/sax) into .agents/skills/spec-change in your project. Codex loads it when a task matches its description.
Can I use Spec Change in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gdsfactory/sax --skill spec-change -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spec-change, .gemini/skills/spec-change, .github/skills/spec-change and .opencode/skills/spec-change in your project.
What does Spec Change need to run?
SKILL.md names no scripts, command-line tools or credentials: Spec Change is instructions for the agent only.
Does Spec Change access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Spec Change safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Spec Change use?
Spec Change is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Spec Change use?
About 852 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Spec Change?
Skills that share tags, products or a category with Spec Change: Qnn (iblameandrew/open-deepthink, 151 stars), Tapd Story Plan (TencentBlueKing/bk-bcs, 840 stars), Tapd Story Tasks (TencentBlueKing/bk-bcs, 840 stars) and OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 71k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Spec Change?
gdsfactory (a GitHub organization) maintains it in gdsfactory/sax, which has 131 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 1, 2026.
Source: gdsfactory/sax on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.