open-knowledge-pack-software-lifecycle-write-a-spec
Scope a feature end to end and write an implementation spec under specs/ from an accepted proposal — current-system mapping, goals/non-goals, a Decision Log for one-way-door choices, a live Open Questions backlog, and a real migration + test plan. Read when asked to write a spec, scope this feature, turn this proposal into a spec, plan the implementation, or break this into tasks. Do NOT fire on frame a proposal or write the PRD (sibling frame-a-proposal — a PRD frames a change before it is accepted; this skill starts once one is), record a decision or write the ADR (record-a-decision), write a postmortem (write-a-postmortem), or review this design (review-a-design) — those are separate skills. Complements the platform open-knowledge skill; does not replace it.
Security AStatic scan found no risk patternsHow grading works ›
From the source SKILL.md
A spec is the contract between "we decided to build this" and "here is how it gets built." It is derived from an ACCEPTED proposal, maps the system that exists TODAY before proposing a change, and records its one-way-door choices in a Decision Log so the reasoning survives the author leaving. A spec that skips the current-system mapping, or resolves its open questions silently, is a liability — it reads authoritative while being unfounded.
What this skill does
open-knowledge-pack-software-lifecycle-write-a-spec is a community-contributed Claude Code skill in the product-misc sub-category. It ships as a SKILL.md file that Claude Code auto-discovers under ~/.claude/skills/write-a-spec/ and loads when your prompt matches the skill's trigger.
Who uses this skill
The open-knowledge-pack-software-lifecycle-write-a-spec Claude Code skill is built for product managers, product designers, and cross-functional teams planning, shipping, and measuring product features. It's part of ClaudSkills (also referred to as Claude Skills or Claude Code Skills) — the open community-curated registry of 211,000+ SKILL.md files for Anthropic's Claude Code agent and the wider Claude ecosystem (Claude API, Claude Agent SDK).
How to install
Free
Manual install (2 steps)
mkdir -p ~/.claude/skills/write-a-spec
curl -L https://claudskills.com/skills/write-a-spec/SKILL.md \
-o ~/.claude/skills/write-a-spec/SKILL.md
Or just download SKILL.md directly and drop it into ~/.claude/skills/write-a-spec/. Claude Code auto-discovers it on next session.
Skills live at ~/.claude/skills/write-a-spec/SKILL.md on macOS/Linux, or %USERPROFILE%\.claude\skills\write-a-spec\SKILL.md on Windows. See the full install guide for step-by-step instructions.
Telegram
📱 Install from your phone or desktop Telegram
Open @claudskills_bot on Telegram, tap Open Desktop App, and the desktop app installs this skill for you. Or share the bot link with a colleague — they get the same one-tap install. Learn more →
Pro
One-click install via the desktop app
The ClaudSkills desktop app installs any skill directly into ~/.claude/skills/ with one click — no terminal required. Pro starts at $9/mo or $149 lifetime.
Pro
For the full experience including quality scoring and one-click install features for each skill — upgrade to Pro.
Frequently asked questions
How do I install the open-knowledge-pack-software-lifecycle-write-a-spec Claude Code skill?
Install via the ClaudSkills desktop app (one click) or copy
SKILL.md from the source repository to
~/.claude/skills/write-a-spec/SKILL.md and restart Claude Code. Both flows are detailed at
claudskills.com/install/.
What does the open-knowledge-pack-software-lifecycle-write-a-spec skill do?
Scope a feature end to end and write an implementation spec under specs/ from an accepted proposal — current-system mapping, goals/non-goals, a Decision Log for one-way-door choices, a live Open Questions backlog, and a real migration + test plan. Read when asked to write a spec, scope this feature, turn this proposal into a spec, plan the implementation, or break this into tasks. Do NOT fire on frame a proposal or write the PRD (sibling frame-a-proposal — a PRD frames a change before it is accepted; this skill starts once one is), record a decision or write the ADR (record-a-decision), write a postmortem (write-a-postmortem), or review this design (review-a-design) — those are separate skills. Complements the platform open-knowledge skill; does not replace it.
Is this skill free to install?
Yes. ClaudSkills is an open registry — every skill keeps its source repository's license, and manual install via copy is free. ClaudSkills Pro ($9/mo, $79/yr, or $149 one-time) adds one-click install via the desktop app and a multi-signal Quality Score.
When should I use the open-knowledge-pack-software-lifecycle-write-a-spec skill?
Use open-knowledge-pack-software-lifecycle-write-a-spec when your Claude Code task falls under the Product category — specifically in the product misc area. Claude Code auto-discovers installed skills and invokes the right one based on the task description, so you can also ask Claude directly (e.g. "use open-knowledge-pack-software-lifecycle-write-a-spec" or describe the task and let Claude pick). Browse related skills at
/category/product/.
What is a Claude Code skill and how does the open-knowledge-pack-software-lifecycle-write-a-spec skill fit in?
A Claude Code skill is a
SKILL.md file that lives under
~/.claude/skills/<name>/ and tells the Claude Code CLI agent how to perform a specific task (instructions, prompts, allowed tools). Skills are auto-discovered at session start. open-knowledge-pack-software-lifecycle-write-a-spec is one of 67,000+ skills indexed in the open ClaudSkills catalog, classified under the Product category. Learn more at
/learn/what-is-a-claude-skill/.
Attribution & license
Cite this skill
If you reference this skill in a blog post, paper, or documentation, you can cite it as:
APA
inkeep. (2026). open-knowledge-pack-software-lifecycle-write-a-spec [Claude Code skill]. ClaudSkills. https://claudskills.com/skills/write-a-spec/
BibTeX
@misc{write-a-spec-2026,
author = {inkeep},
title = {open-knowledge-pack-software-lifecycle-write-a-spec [Claude Code skill]},
year = {2026},
publisher = {ClaudSkills},
url = {https://claudskills.com/skills/write-a-spec/}
}Embed this skill
Promote, attribute, or link this skill from your own README, blog post, or documentation. All three snippets are free to use — no sign-up, no API key. More distribution surfaces →
Badge
[](https://claudskills.com/skills/write-a-spec/?utm_source=badge&utm_medium=readme&utm_campaign=skill_badge)
<script>
<script src="https://claudskills.com/embed/write-a-spec.js" async></script>
<iframe>
<iframe src="https://claudskills.com/embed/write-a-spec.html" width="100%" height="160" frameborder="0" loading="lazy" title="ClaudSkills: open-knowledge-pack-software-lifecycle-write-a-spec"></iframe>
Security scan
Grade A · scanned 2026-10-25 — free static scan against the OWASP Agentic Skills Top 10.
The scan flagged 1 of 10 categories (execution), including lower-severity patterns. Patterns shown inside code fences are weighted as examples rather than instructions — read the grading methodology for what this does and does not guarantee.
- ✓ Prompt injection
- ✓ Data exfiltration
- ✓ Supply chain
- ✓ Reverse shell
- ✓ Credentials
- ⚠ Execution
- ✓ Filesystem
- ✓ Persistence
- ✓ Obfuscation
- ✓ Network
Show this grade on your repo (click to copy):
[](https://claudskills.com/skills/write-a-spec/#security)
More Product skills
Browse all Product skills in the ClaudSkills registry, or explore these other picks from the same category:
Part of Acreator Store — Adam Lankamer's AI tools:
PerfectStudio ·
Ucaption ·
UTagger ·
AutoXPoster ·
TestYourSkills ·
AutomationFlows ·
Au Naturel ·
Telegram @acreatorstore