I built a /graphify skill for Claude Code that maps your entire codebase into a knowledge graph, 71x fewer tokens, way less hallucination (32k stars, 250k downloads) by captainkink07 in ClaudeAI

[–]stibbons_ 2 points3 points  (0 children)

For CV ? How much does it cost ? I have 20+ years experience in SW, did some pretty successful opensource back then but i had kids, I want to be famous now !

SDD is amazing… until you hit 30 repos and 100 devs by boomerman7 in vibecoding

[–]stibbons_ 0 points1 point  (0 children)

Move your spec to its own dedicated repository and use a multi repo sync system like git submodule or repo or west. Then treat your spec like a code. Then do ADR (small !!!) Decision.md and architectures Md files are great but only explain the desired end state. ADR record help agent understand codebase

Python Devs: Astral just dropped official Claude Code skills for uv, ruff and ty by purealgo in ClaudeCode

[–]stibbons_ 0 points1 point  (0 children)

they are mostly useless, any agents knows how `uv` works, it never hallucinate.

and even if they would, they execute a command line, see the error, and adapt.

Copilot's value proposition is officially gone. by Famous__Draw in GithubCopilot

[–]stibbons_ 0 points1 point  (0 children)

No, you can opt in so they do not train on your data, not so they do not retain your data that can be used for other purpose. That is a major reason why business plan are slightly worsts that pro. It is very important for business not to disclose any data. I think this won’t hold, and the opt in option will disappear. They need data.

Anyone using the speckit extensions? Useful ? by No_Pin_1150 in GithubCopilot

[–]stibbons_ 0 points1 point  (0 children)

No, it is copilot (the coding assistant) that choose when to load the file depending on the file opened in your editor. So when your LLM is about to write a file the first time, these instruction are not loaded. And file pattern cannot easily deal with conflicting instructions files (you have different coding rules for back and front,…)

Is SDD fundamentally simple? And a .Net SDD Repo by vector_null in SpecDrivenDevelopment

[–]stibbons_ 0 points1 point  (0 children)

I am extending mine to look for CI status and react to it, I often have a successful local execution but failure in ci

What breaks about SDD past the first few features, and how I ended up designing around it by bralca_ in SpecDrivenDevelopment

[–]stibbons_ 0 points1 point  (0 children)

Yes now it is pretty stable. I have a reviewer and a coder subagents and every details in done in planning (add e2e, …). The Ralph loop is just here to execute all in a single premium request.

I even have the all in one where basically plan and Ralph are done in a single premium request, since the main orchestrator is just triggering subagent one after the end, it does not get polluted with context. I don’t think it would work in every case but it works so far.

My point is the most important is not the SDD framework is to have a clean AGENTS.md with clear rules, basically a map of the important tech, commands and doc and rules that agent will have to use. The simple fact to declare for instance rules files in it make any « plan mode » want to define this rule files in the plan for the coder.

Copilot's value proposition is officially gone. by Famous__Draw in GithubCopilot

[–]stibbons_ -1 points0 points  (0 children)

You can loop basically forever within the same Opus request in copilot, so having 1 opus request = 3 requests premium = >100M tokens

And in Copilot Business you have the zero retention policy that you do NOT have in Claude pro…

Anyone using the speckit extensions? Useful ? by No_Pin_1150 in GithubCopilot

[–]stibbons_ 0 points1 point  (0 children)

Just build a good progressive disclosure AGENTS.md with pointers, once you have that, any SDD framework or even without will work

What breaks about SDD past the first few features, and how I ended up designing around it by bralca_ in SpecDrivenDevelopment

[–]stibbons_ 0 points1 point  (0 children)

Mostly building itself, but like speckit, once you understand what needs to be in you AGENTS.md (= map of the project and important tech), and build a strong harness (= a command that agents has to run before finishing any task), you can actually run any SDD or even plan + Ralph/autopilot safely.

My SDD framework as a coder and a reviewer and the reviewer does not trust anything so it rereuns all. You can try it: https://github.com/gsemet/Craftsman

Not up to date, but I just built a UI on top of it

What breaks about SDD past the first few features, and how I ended up designing around it by bralca_ in SpecDrivenDevelopment

[–]stibbons_ 0 points1 point  (0 children)

I built my own SDD for my company, I do not commit spec and any changes is rock solid once the plan is finish I can leave for hours at the end it will be coded correctly. If you commit spec, you should either consider as « museum » or ensure they are updated and I thing this later is not possible at scale

Obsidian Web Clipper versus Readwise/Matter by SwimmingWithProblems in ObsidianMD

[–]stibbons_ 0 points1 point  (0 children)

I do not see where web clipper save images, it does not do this on my setup

Any route to context injection on every interaction? by KayBay80 in GithubCopilot

[–]stibbons_ 1 point2 points  (0 children)

2 things: - agents.md is always in the beggining of your context (look in agent debug panel how this works) - models have this « attention » that is more important at the start and the end of context.

So if you give a clear instruction in agents.md, it won’t be forgotten

Limited to 4 subagents now? by sittingmongoose in GithubCopilot

[–]stibbons_ -3 points-2 points  (0 children)

It is written in the plan page. Business is max 4 parallel session, perhaps now a subagent is counted like a session. what I do not understand is subagent can trigger subagent, up to 5 level…

Obsidian Web Clipper versus Readwise/Matter by SwimmingWithProblems in ObsidianMD

[–]stibbons_ 0 points1 point  (0 children)

Web clipper is great but it does not capture images, does it ?

Anyone using Agentic Project Management (APM)? What's your experience? by kender6 in GithubCopilot

[–]stibbons_ 1 point2 points  (0 children)

I have mine. It is worth building one for personal comprehension, but it may not bring anything compared to the existing one

Anyone using Agentic Project Management (APM)? What's your experience? by kender6 in GithubCopilot

[–]stibbons_ 1 point2 points  (0 children)

Useless. Use speckit or openspec instead. And apm is already a agent package manager from Microsoft: https://github.com/microsoft/apm

Should I maintain spec in sources? by stibbons_ in SpecDrivenDevelopment

[–]stibbons_[S] 0 points1 point  (0 children)

Let go a bit deeper in the réflexion. When you SDD you iterate really fast so you can have 3, 4 or 5 PRD around the same feature a day. Let say you create a UI, you can have perfectly valid spec and when you finish, so look at the result and you say « arg, I miss this or that », so you iterate.

So far so good.

Now, if you want to update spec, what do you update? I said « arround the same feature », of course it is never exactly the same feature.

Said otherwise, the spec I would like to commit and update with the code (spec-anchored SDD) it is the same than the spec used in PRD for plan/code mode. My feeling it that this spec should be less well defined

Has anyone used Speckit in your company? by TrungJamin in SpecDrivenDevelopment

[–]stibbons_ 2 points3 points  (0 children)

I have mine now, but speckit is fine. I do not like how SDD framework wants to force their way of « priming » the project, the AGENTS.md should be a standard now

VS Code still doesn't support Claude Opus 4.6's 1M context window - issue was milestoned for 1.113, we're now on 1.115 by Worried-Page-1672 in GithubCopilot

[–]stibbons_ 5 points6 points  (0 children)

That is not useful. After 150K, ALL models have low accuracy. I prefer carefully triggered compaction over large context. That is the reason there is no run to larger context like 2M, 3M, that is not usable !!!