write-a-spec

write-a-spec is an Engineering planning & specs skill for AI agents, published by inkeep in the open-knowledge repository on GitHub. Skillspace rates write-a-spec F (45/100) and the safety scan rated it risky; the rating is based on static analysis only.

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.

Grade
F
Quality
45 / 100
Safety
Risky
GitHub stars
4,197

Unproven: rated by static analysis only, not yet compared head-to-head.

This rating describes the version of the repository we crawled; it may have changed since.

Our review

Architecture
92 / 100
Maturity
Basic: a single SKILL.md
Security scan
High-risk patterns
License
Not declared. Check the repository before reusing it.

What the scanner flagged

  • dynamic code execution (eval/exec)

Not checked yet

  • Category is a classifier prediction; no model has read this skill yet
  • Not judged on the rubric yet (not a contender in its category)
  • No blind task eval yet
  • Scope (portable / vendor / repo-internal) not assessed; only the top of each category is read for scope
  • Sibling files (scripts, references) not fetched; security scan covers SKILL.md only

Skillspace indexes and rates this skill; it does not host or endorse it. Run third-party skills at your own risk.