port-spec
SolidLyra'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.
Install
Quality Score: 83/100
Skill Content
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
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.
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").
port-codebases
Plan, execute, review, and verify behavior-preserving codebase ports across programming languages, runtimes, frameworks, platforms, storage engines, or major APIs. Use when asked to rewrite or migrate an implementation while preserving semantics, mechanically translate a large body of code, replace a runtime or language, run a strangler or big-bang port, turn compiler and test failures into a migration queue, or organize AI-assisted porting with one or many agents. Scale the workflow to the available time, compute, and model budget without weakening correctness gates. Do not use for ordinary dependency bumps, small local refactors, or product redesigns disguised as a port.