forztf/open-skilled-sdd
5 skills3.9k installs45 starsGitHub
Install
npx skills add https://github.com/forztf/open-skilled-sddSkills in this repo
1Openspec ImplementationOpenspec-implementation is an agent workflow for solo builders using spec-driven development: after a proposal is approved, the skill forces disciplined execution against tasks.md under spec/changes/{change-id}/. It mirrors a six-step checklist—understand the proposal, stand up TodoWrite tracking, run tasks in order, test each slice, refresh living specifications when the OpenSpec model requires it, and close the change as implementation-complete. The hard gate is honesty on completion: incomplete work must not be checked off. That makes it ideal when your agent tends to jump ahead or batch edits without verification. It spans Build (coding) and Ship (testing, validation) but shelves under Build PM as the handoff from planning artifacts to code.907installs2Openspec Proposal CreationOpenSpec Proposal Creation is an agent skill for solo builders who want spec-driven development instead of jumping straight into code. It walks you through reviewing current specifications, minting a change ID, scaffolding folders, and drafting a concise proposal that explains why the change matters, what will change, and what it affects. In parallel it builds a numbered tasks.md implementation checklist and a spec-delta.md file that records formal requirement edits using ADDED, MODIFIED, and REMOVED semantics with EARS-style requirements. The workflow ends with structural validation and a deliberate approval step so your coding agent has an ordered plan and an auditable spec diff. It fits early Validate work when you are scoping a feature or architecture shift, and it remains useful in Build when you need PM-style change packages that downstream agents can execute without reinterpretation.810installs3Openspec Proposal Creation CnOpenspec-proposal-creation-cn 是面向独立开发者与小团队的中文 OpenSpec 代理技能，在动手编码前把「想法」收成可审批的变更包。它要求先审阅 spec/specs 与进行中的 spec/changes，生成唯一 change-id，按模板搭建 spec/changes/{id} 目录，并同步撰写提案摘要、可执行 tasks.json 与规范差异文档。工作流强调结构与验证，最后向用户展示并请求批准——适合技能驱动或规范驱动仓库，而不是即兴聊天式需求。技能横跨 Validate 定范围与 Build 前期 PM，但 Prism 主架仍落在 Validate 的 scope，便于在目录里与英文规划技能对照检索。需要已存在或计划采用 OpenSpec 目录布局的仓库。776installs4Openspec Context Loadingopenspec-context-loading is an agent skill for teams using OpenSpec-style spec directories. Solo builders invoke it when they need ground truth about project state—what capabilities are documented, which change proposals are active, and where a feature is defined—without manually spelunking the repo. The skill encodes a repeatable discovery loop: run find/tree-style commands on spec/specs and spec/changes, read the relevant spec.md files, then summarize capabilities and requirements in plain language. It fits early in a coding session, before authoring a new change, or when an agent must not contradict an existing requirement. For Prism’s journey, it bridges validate-style scope questions and build-phase execution because specs are the source of truth agents should load first. It is procedural knowledge packaged as SKILL.md, not an MCP server or external API integration.722installs5Openspec Archivingopenspec-archiving is an agent skill for teams using OpenSpec-style change proposals. After implementation and deployment, solo builders invoke it when a change is ready to retire from the active queue and its specification deltas must become part of the living spec rather than staying in a transient changes folder. The workflow enforces completion checks, walks through delta review, performs structured merges into canonical spec files, and relocates the change into an archive with a timestamp so history stays traceable. It pairs naturally with earlier proposal and implementation skills in the same repository. Use it when triggers like openspec archive, merge specs, complete proposal, or finalize spec appear—not while design or coding is still in flight. The outcome is documentation that matches what shipped and a clean changes directory for the next initiative.671installs