HN Showcase
Back to browse
Specifica – an open format for writing software specs as Markdown

Specifica – an open format for writing software specs as Markdown

by openmason·Mar 17, 2026·1 point·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidBig BrainSlick

Three-file convention forces clarity—what, how, and work stay separated for humans and LLMs.

Strengths
  • •Plain markdown in Git repo means zero lock-in and works in any editor.
  • •AI-optimized structure gives LLMs consistent context for requirements and decisions.
  • •npm packages for parsing enable tooling ecosystem around the format.
Weaknesses
  • •Spec formats are crowded—ADRs, RFCs, and Notion templates already exist.
  • •Adoption depends on teams buying into the convention over existing workflows.
Target Audience

Software teams, technical writers, developers documenting architecture

Similar To

Architectural Decision Records · Notion templates · Swagger/OpenAPI

Similar Projects

Developer Tools●●Solid

Turn any OpenAPI spec into agent-callable skills

It extracts focused, executable operations from giant OpenAPI files (the GitHub REST YAML is shown) to shrink context and avoid sidecar adapter sprawl — a pragmatic answer to token bloat and brittle ad-hoc integrations. Useful and concrete: if it actually generates tidy, updateable skill units and runtime hooks it saves a lot of maintenance. That said, the idea competes with existing LangChain/openai-function patterns; the repo will need clear runtime, versioning, and update strategies to feel like more than a nicer converter.

Solve My ProblemNiche Gem
yz-yu
103mo ago