port-spec

Solid

Lyra's spec-port skill. Takes a complete written specification and ports it into working code or a vault artifact. Confirms scope, reads the target, builds, returns honesty ledger.

AI & Automation 11 stars 3 forks Updated today MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
36
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
81
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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 sur...

Details

Author
wrg32786
Repository
wrg32786/aigent-os
Created
1 months ago
Last Updated
today
Language
JavaScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Featured

openspec-plus-spec

MANDATORY skill that activates whenever the OpenSpec specification phase begins. Triggers: /opsx-new, /opsx-ff, or /opsx-continue runs; openspec-new-change, openspec-ff-change, openspec-continue-change, or openspec-explore is active; `openspec instructions spec` or `openspec instructions specs` is invoked; or the user wants to create, update, review, refine, or discuss an OpenSpec specification.

133 Updated 3 days ago
sudokar
AI & Automation Solid

spec-forge

Professional specification system for Codex. Use when the user asks to create, improve, review, audit, analyze, or propagate product/software documentation, including ideas, PRDs, SRS documents, technical designs, architecture/RFC docs, feature specs, test cases, documentation audits, document landscape analysis, and full idea-to-spec chains. Supports complex multi-skill orchestration: idea -> decompose -> tech-design + feature specs -> review, with optional PRD, SRS, test-cases, audit, analyze, and propagate workflows.

5 Updated 1 weeks ago
tercel
AI & Automation Listed

legacy-spec-agent

Reverse-engineer a specification from undocumented legacy code, and track drift between the code and that spec. Use this whenever the user wants to understand what an unfamiliar or undocumented codebase actually does, onboard onto legacy code, generate the missing spec/documentation from source, reconstruct business rules or architecture from code, or detect when code has diverged from its documented intent — even if they never say the word "spec" (e.g. "what does this repo actually do", "document this legacy system", "I inherited this codebase and there are no docs", "did anything break the original design").

0 Updated today
HoonStyle