port-spec — Claude Code skill: what it does, how to install
The port-spec Claude Code skill turns a complete written specification into code or a vault artifact. It activates for spec implementation, brief-based builds, and ports from specs.
MIT ★ 26 updated 2026-11-16
npx skills add wrg32786/aigent-os --skill port-spec -a claude-codeWhat port-spec does
port-spec converts a written specification into working code, configuration, or a vault artifact. It handles schemas, data models, API contracts, vault note structures, and component designs. Before changing anything, it reads the target files and searches for related types, imports, and dependencies.
The work stays within the brief. If a requirement is ambiguous, the skill asks one focused question; if the task exceeds the stated scope, it stops and reports what remains. Each delivery includes an honesty ledger covering changed and untouched files, out-of-scope issues, uncertainty, tradeoffs, and unfinished work.
What it helps with
- turn a data schema from a spec into code
- implement an API contract from a written brief
- create a vault artifact from a defined structure
- report work that falls outside the specification
Example prompts for the agent
- Port this specification into the project code.
- Implement the API contract from this brief.
- Create a vault artifact that follows this structure.
How to install port-spec
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill port-spec -a claude-code2Manually: put the files in place
~/.claude/skills/port-spec/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/port-spec/
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill port-spec -a codex2Manually: put the files in place
.agents/skills/port-spec/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill port-spec -a cursor2Manually: put the files in place
.cursor/skills/port-spec/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wrg32786/aigent-os skills/port-spec2Manually: put the files in place
.github/skills/port-spec/SKILL.md1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill port-spec -a gemini-cli2Platform CLI
gemini skills install https://github.com/wrg32786/aigent-os --path skills/port-specManually: put the files in place
.devin/skills/port-spec/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill port-spec -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about port-spec
How do I install port-spec in Claude Code?
Run npx skills add wrg32786/aigent-os --skill port-spec -a claude-code. The skill file is at ~/.claude/skills/port-spec/SKILL.md.
What does port-spec do?
It turns a complete written specification into code, configuration, or a vault artifact. It reads relevant project files before editing and returns a ledger of changes, open issues, and unfinished work.
How does port-spec handle ambiguous requirements or scope changes?
It asks one focused question when a requirement is ambiguous. If the work goes beyond the brief, it stops and reports what remains instead of expanding the task.
Source text
SKILL.md · MIT
--- name: port-spec agent: lyra description: "Turn a complete written specification into working code or a vault artifact. Use when implementing a spec, building from a brief, or porting a spec to code." allowed-tools: Read, Write, Edit, Bash, Grep, Glob, Agent user-invocable: true triggers: - port this spec - implement this spec - build from spec - port spec - implement from brief - execute this brief - build this - port to code --- # Port Spec You are Lyra executing a bounded port from a written specification to a working artifact. ## What this skill does Take a complete specification (schema, data model, API contract, vault note structure, or component design) and port it into working code, config, or a vault artifact. No strategy. No scope expansion. Build what the spec says, return what changed. ## Protocol ### Step 1: Confirm scope (one sentence) Read back the spec in one sentence. Example: "Porting the User schema from the spec into a TypeScript interface at `src/types/user.ts`." If anything is ambiguous, ask ONE focused question. Then build without further interruption. ### Step 2: Read the target Before writing a single line: - Read the target file(s) if they exist - Grep for related types, imports, or dependencies - Understand what's already there ### Step 3: Build Execute the port exactly as specified. Stay within scope. If the work expands beyond the brief, STOP and surface it — do not build unilaterally. ### Step 4: Return honesty ledger ``` ## Honesty Ledger **Changed:** <list of files modified or created> **Untouched:** <files read but not changed> **Noticed-not-fixed:** <issues seen but out of scope> **Residual uncertainty:** <anything you had to guess> **Tradeoffs:** <decisions made where alternatives exist> **Stopped-short:** <scope boundary hit — what's left> ``` ## Constraints - Read before writing. Always. - One clarifying question allowed, then ship. - Scope creep surfaces back to the composer — never expands unilaterally. - Honesty ledger is non-negotiable on every delivery.
© wrg32786 · MIT · wrg32786/aigent-os