HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Fission-AI
OpenSpec
TypeScript2025–2026
Fission-AI / OpenSpec

OpenSpec

Spec-driven development (SDD) for AI coding assistants.

11Distinct people
13Mentions
0Explicit recommenders
74.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Spec-driven development (SDD) for AI coding assistants.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

How I'm fighting the AI brain fry direct repository linkDebated

The discussion centers on whether AI coding assistants cause cognitive overload and skill atrophy, with some users advocating for manual practice like LeetCode to maintain sharp problem-solving abilities while others argue that the real issue is managing parallel workstreams and context switching. A significant portion of the conversation critically examines the original author's use of AI to write a post about avoiding AI brain fry, highlighting a perceived hypocrisy and criticizing the resulting text style.

215 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4

Mentions over time

HN mentions by month13 dated mentions

Observed mentions: 2025-10-22 01:18:24 UTC to 2026-10-15 12:22:59 UTC.

01232025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 20252025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 commentsApr 20262026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-01 00:00:00 UTC to 2026-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-10-01 00:00:00 UTC to 2026-11-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC101
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC000
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC110
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC101
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC312
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC220
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC303
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC000
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC000
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC000
Sep 20262026-09-01 00:00:00 UTC2026-10-01 00:00:00 UTC101
Oct 20262026-10-01 00:00:00 UTC2026-11-01 00:00:00 UTC101

What Hacker News says

13 sources

Show HN: OO – Automated O&O Shut-Up for Windows

Why use Windows? Well, some people do. Why let Microsoft spy on your content? Why indeed? So, O&O Shut-Up (https://www.oo-software.com/en/shutup10) claims to cut the connection and telemetry between you and Microsoft. However, when Microsoft updates your computer, the settings are reset, and you have to run O&O ShutUp again. Why not run OO which installs PowerShell 7+ if not installed, O&O Shutup, then it makes a scheduled tasks that runs the default settings after every Microsoft update? Why futz around with re-running anything? Just run OO once, and forget it. Please file any bugs if you find them. This isn't really going anywhere except to help internet users and my clients. Hope it's helpful PS - All of it generated with VS Code, Augmentcode AI (https://www.augmentcode.com/), OpenSpec (https://github.com/Fission-AI/OpenSpec), and
Read the rest
1 points · Open discussion

Show HN: MTTCleaner – Same as CCleaner but free, no ads

I'm an IT consultant. CCleaner was a good choice to speed up clients' web browsing experience. Unless you paid, it keeps vomiting ads for the product. Which made it a bad choice. mTTCleaner does most of the same thing to clean most browsers by cleaning caches, compacting databases, and removing unnecessary metrics files. It can create it's own cron job/scheduled task to run itself every month, if you choose. It covers 28 browsers on 3 platforms, assuming you have PowerShell 7+. Please file any bugs if you find them. This isn't really going anywhere except to help internet users and my clients. Hope it's helpful PS - All of it generated with VS Code, Augmentcode AI (https://www.augmentcode.com/), OpenSpec (https://github.com/Fission-AI/OpenSpec), and beads (https://github.com/gastownhall/beads).
1 points · Open discussion
This is the second endorsement I've seen today. I gave OpenSpec a shot and was dismayed by the Explore prompt. [1] Over 1,000 words with verbose, repetitive instructions which will lead to context drift. The examples refer to specific tools like SQLite and OAuth. That won't help if your project isn't related to those. I do like the basic concept and directory structure, but those are easy enough to adopt without all the cruft. 1. https://github.com/Fission-AI/OpenSpec/blob/main/src/core/te...
In Get Shit Done: A meta-prompting, context engineering and spec-driven dev system

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.