Bossie
Joined 5 years ago
Karma
9
Submissions
7
Member since
Nov 30
Recent submissions
Comment · 2 months ago
Comment · 2 months ago
Not only Opus, here's Fumble 5:
> I'll script the bulk transform, then hand-fix the残 assertions:
Comment · 3 months ago
Every time I enter an elevator, I wonder whether it will be the first one I've come across that supports deselect.
Comment · 4 months ago
I'm currently rolling out Matt Pocock's Sandcastle project so that I can have those brakes removed. What will be left is just the grilling(/wayfinding).
My current flow heavily relies on Matt Pocock's Skills and Sandcastle project. I find them highly valuable in practice: grilling(/wayfind) into a spec and extract issues. Those live in Linear projects. I'm pointing my Sandcastle set-up at such Linear projects (or loose issues), which results in an MR.
Currently at the point of self-improving the prompts and Sandcastle set-up with a retrospective pass of the logs.
Comment · 6 months ago
Building a multi-app monorepo for apps which integrate with a Dutch ERP vendor. I'd say the size of those apps is fairly small.
Also building out an MCP server.
Comment · 6 months ago
My workflow is also highly inspired by Matt's skills, but I'm leveraging Linear instead of Github.
/grill-me (back-and-forth alignment with the LLM) --> /write-a-prd (creates project under an initative in Linear) --> /prd-to-issues (creates issues at the project level). I'm making use of the blockedBy utility when registering the issues. They land in the 'Ready for Agent' status.
A scheduled project-orchestrator is then picking up issues with this status leveraging subagents. A HITL (Human in the loop) status is set on the ticket when anything needs my attention. I consider the code as the 'what', so I let the agent(s) update the issues with the HOW and WHY. All using Claude Code Max subscription.
Some notes:
- write-a-prd is knowledge compression and thus some important details occasionally get lost
- The UX for the orchestrator flow is suboptimal. Waiting for this actually: https://github.com/mattpocock/sandcastle/issues/191#issuecom...
- I might have to implement a simplify + review + security audit, call it a 'check', to fire at the end of the project. Could be in the form of an issue.
Comment · 8 months ago
What is being researched? Any objective?
All prove great value.