What Difference Does the Coding-Agent Method Make?
Building with coding agents, Agent Skills, Superpowers, Spec Kit and /goal changed my question from which toolkit is better to what each layer actually changes.
From Building a Solution to Validating a Product
I stopped building for a moment and applied Product Discovery to CAS. The biggest lesson: a working solution proves capability, not that a product matters.
Judgement before generation
Editorial judgement not generation was the constraint. Explicit selection, convergence and articulation turned direct publishing into a governed workflow.
From career knowledge to reusable evidence
Interview preparation became a reusable workflow grounded in Portfolio evidence, with real opportunity runs showing that output validation matters beyond implementation.
When the learning wasn't the problem, the publishing workflow was
After six months of Weekly Learnings, I realised reflection worked but public communication didn't. I added an explicit editorial reasoning layer between reflection and publication.
From reactive governance to controlled architecture evolution
CAS prevent drift at the point of change and detect and govern what still emerges.
CAS Governance Operationalisation and AI Native Architecture Positioning
Evolved the portfolio from a static showcase into an operational architecture platform, embedding lightweight governance into workflows and standardising on an 'AI native' delivery model.
Refactoring as Discovery: Stabilising Through Boundaries and Explicit Contracts
System instability was traced to extended refactoring, leading to a shift towards explicit boundaries, single-source persistence, and orchestration-owned execution.
Stabilising the Architecture: Pipelines, Parallel Agents, and Governance
Refactoring the system from an orchestrator model into explicit pipelines revealed the need for continuous architecture governance to avoid architectural drift.
From Hardening to Positioning: Closing the Architecture Loop
Focused on closing the observability and boundary-hardening loop, raising architecture maturity and shifting to MVP value delivery.
From Agents to Architecture: Determinism, Observability & Provider Boundaries
Hardened the Runner Agentic Intelligence spine: deterministic analytics replaced agent-driven computation, observability matured, and LLM providers were centralised behind LiteLLM.
Formalising the Pattern Publication System
This week focused on evolving and stabilising the Architecture Pattern system by aligning process and governance rules into a coherent publication pipeline.
From rapid iteration to a publishable system
This week focused on consolidating rapid experimentation into a repeatable system, aligning architecture, process, and UX in preparation for real user exposure.
Stress-testing the Ideas to Life system under real agentic load
This week focused on applying the Ideas to Life process to a running experiment, using real constraints to refine how decisions, tooling, and documentation interact.
From ad-hoc prompts to a coherent learning system
This week focused on stabilising workflows and reframing Weekly Learning as a synthesis layer, reducing drift while enabling multiple learning threads to coexist.
Stabilising the foundation before scaling experiments
A week focused on stabilising infrastructure and reducing technical friction instead of shipping new experiments.
The Power of Small Experiments
Why starting small and shipping often beats perfectionism every time.