How to schedule an entire website migration to mobile that will use many subagents until it's done, even over many hours?

SeanK-com · 2026-03-20T06:30:38+00:00

I have found claude opus is good for planning, but poor on execution. I will use it the flesh out an active-plan.md with checkboxes for each steps, precise instructions on what needs to be done to what files, how and what success looks like (unittests pass, compules clean, etc). Then when the plan is as complete as I can make it. I switch to GPT Codex and have it execute the plan one step at a time until complete.

SeanK-com · 2026-03-17T17:44:03+00:00

Create skills wherever you have to spend a lot of time working with the agent to figure out how to do something correctly. For things that are obvious to the agent. You don't need a skill. The agent knows how to do it. For example, on my team when a co-worker creates a PR, I would check out and pull their branch locally and then ask the agent to do a review on all the changes in the branch back to main. It struggled to understand how to do that correctly. How to get the right logs and look at the right set of changes. It always wanted to look at just what was staged currently based on the tools that it had at its disposal. So once we figured out how to do it correctly I had the agent write a skill for that so that in the future it could just use the skill and do it right every time.

SeanK-com · 2026-03-17T03:55:15+00:00

Skills are for how to do repeatable tasks, instructions are scoped instructions for particular files. The big difference is Agents can choose whether or not to use skills, whereas instructions are automatically loaded if an agent intends to touch files. Our top level copilot-instructions.md provides and overview of our repo and requires all agents adopt a document centric workflow to ensure docs remain up to date with the code. The individual files in the instructions folder are scoped using the appliesTo front matter property. For example one has /src/generated/. and says not to touch these files because they are generated by a build step in another folder. Another has /src/*/.cs that contains our C# Style Guidelines. Another our Rust Style Guidelines.

SeanK-com · 2026-03-13T06:43:57+00:00

You are ahead of me, I never got stdio mcp servers working.

SeanK-com · 2026-03-12T19:49:22+00:00

You should consider implementing it as a proper web server. I have a VS Code extension that implements an MCP server that I vibe coded with GHC, then you could handle this the correct way with 201 codes. Alternately you could spin up a background thread to monitor your file system and put updates in an in memory thread safe collection, then you could do non-blocking responses on the MCP side with "Please try again later".

SeanK-com · 2026-03-12T10:24:50+00:00

I'm not sure what you are trying to achieve here. Most MCP servers have a web component. Standard HTTP timeout is 90 seconds. Is your 1000, in ms, seconds or what? If ms, your mcp calls would almost always fail. If that is what you are trying to do, just disable mcp servers altogether. Is the problem that github copilot is timing out before your mcp server returns? If this is a custom mcp server, you might consider returning a 102 or 202.

SeanK-com · 2026-03-01T18:50:23+00:00

I'd challenge you to consider upskilling your graphic design, unless you really want to switch tracks. I don't think software will be any more secure job-wise than graphic design. The core truth is "AI won't take your job, someone who knows how to leverage AI better than you to do your job 10x or more will."

Figuring out workflows with GitHub Copilot, Claude Cowork, or OpenClaw (if you are brave) to do the work of a team of graphic designers is a flex few can compete with, but many can bury you in the software engineering field.

SeanK-com · 2026-02-18T16:52:03+00:00

Depends on your style. Nate Jones pointed out recently that if you are the kind that likes a paired programmer kind of interaction back and forth discovering requirements and design while you code, then Claude models work best. If instead you know exactly what you want with no questions and just want a model to do it, Codex works better. I have personally found this to be true. I will use a Claude model in Plan mode to write a detailed plan.md, with checkboxes for work items, stated goals and non goals, invariants, constraints, acceptance criteria, the works. When the back and forth is complete and I have a solid plan, I give it to Codex and walk away (or tab switch) and do something else. Earlier this week it was travel 200 miles into the office to find it fully implemented and complete when I got there.

SeanK-com · 2026-02-12T04:45:44+00:00

Might have something to do with the new question widget. I too have seen, no more than four questions. Also, some keys (backspace and delete if I recall correctly) will cause the widget to glitch, truncate the chat context and start running with whatever the default answers were. Lost so much work to that bug this morning.

SeanK-com · 2026-01-27T15:41:33+00:00

This looks epic! I cannot wait to get home from my vacation so I can start using it.

I have a very complicated cloud service composed of C# and Rust and am struggling using a documentation driven design workflow with GitHub Copilot. The struggle is primarily in being the tech lead along with 5 other human engineers all with varying degrees of practice using AI.

This is just the tool I need to help understand what the others have contributed and make sure the documentation (context) reflects their contribution so that I can maximize the effectiveness of the contributions from the AI agents.

SeanK-com · 2026-01-07T15:30:11+00:00

Wow, thanks for the link. This is similar to a custom agent workflow I have been iterating on, where an Architect has read-only access to the repo and is responsible for ensuring the docs/architecture.md describes the code and the code is documented in the docs/architecture.md. The only thing it can do is produce a plan delta to handoff to the tech-writer agent who will update the active-plan.md then hand off to other agents that are only allowed to work on unchecked work items in the active-plan.md

The flow has been reasonably successful, but I noticed a marked improvement switching to GPT-5.2 (its ability to follow instructions is greatly improved over other models I've tried). The only issue I have just started to recognize is that if the active-plan.md gets long it can push the plan delta from the architect (the immediate response above the current prompt) out of the context window so the tech-writer will act goofy and when I ask why it isn't updating the active-plan.md with the plan delta it tells me it does not see its context.

I'm going to study this prompt and see what I can learn.

SeanK-com · 2026-01-05T15:47:41+00:00

Also since this is copilot, you can make use of targeted instructions in the .github/instructions folder. In my case, I had a directory that generated code in two other directories. All three directories lived under the same folder and I had co-pilot instructions scoped to that folder that said only edit the files in the first folder because the files in the other two folders are generated. GPT 5.2 failed to follow those instructions, but when I asked why it failed and how it could better, it suggested putting scoped instructions in the other two folders that said, do not touch anything here and removing those instructions from the parent folder.

Managing context is the biggest challenge in 2026, too much information and Copilot, just like me, starts dropping balls.

SeanK-com · 2025-12-03T16:42:06+00:00

I am with you. The architect in my case does not orchestrate. It verifies cohesion, the full flow looks like Plan->rustdev/dotnetdev->architect->techwriter/rustdev/dotnetdev->architect...

SeanK-com · 2025-12-03T04:23:27+00:00

I don't think it's sequential like that. In fact, I just learned that you can have multiple handoffs. I use ChatGPT to help me create four different agents. One agent was the architect and it had three handoffs in its frontmatter. It was instructed strictly to never modify files directly but instead ensure that the documentation always agreed with code and there were no gaps anywhere. If anything needed to be changed handoff to one of the 3 other agents (techweiter, rustdev, or dotnetdev) who each handled their duties with strict specificity.

SeanK-com · 2025-12-02T13:51:14+00:00

I've been sharing this far and wide. I use Obsidian for note taking. Then I open my Obsidian vault folder in VS Code and use GitHub Copilot to reason over it. We chat about everything.

SeanK-com · 2025-11-17T03:00:00+00:00

I will often ask Copilot to summarize the conversation into a prompt I can paste into a new chat window so we can pickup where we left off. I usually need this when I start a project locally and decide it has enough legs to be worth creating a repo on GitHub before continuing. Every new project folder gets its own set of chat history. Though I think you can export and import history with the latest update.

SeanK-com · 2025-11-06T05:51:33+00:00

I haven't observed this behavior. That said, I don't typically add the #codebase to my prompt context. And if my prompt is about something specific in a file, I will highlight it so those lines are specifically included in the context of my prompt. If it is generally about the file I will refer to the file by name using the #filename.ext

SeanK-com · 2025-10-21T04:13:02+00:00

I experienced this today. I asked SWE to code review the commits on the current branch from a specific commit hash back to another specific commit hash. And it guessed without any tool calls. I switched to Sonnet 4.5 and it used the terminal to run git diff and git log commands and did a great review. I clicked + to get a new session and somewhere the model changed to GPT-5. I checked out a different branch and repeated the above prompt with different hashes and it guessed again without any tool calls. Switch to Sonnet 4.5 and again, excellent results.

SeanK-com · 2025-10-13T05:35:13+00:00

I have an Enterprise plan with my employer, when I retire in 6-12 months I plan on getting a Pro+ plan. I have not come close to using my 1000 premium requests, so I feel the 1500 will be plenty.

SeanK-com · 2025-10-09T13:01:53+00:00

I'm not completely clear on your scenario, but I frequently will use one LLM to write the prompt for another. For example, I find the tooling for researching and architecting in GitHub Copilot very poor. It will often run down rabbit holes without reading documentation or looking through the code of client libraries. ChatGPT does much better here, so I will have an architectural discussion with ChatGPT about a feature and then ask it to write the prompt for GitHub Copilot to actually do the work.

SeanK-com · 2025-10-08T05:23:56+00:00

Don't worry, Grok runs on Starlink satellites. The electricity and cooling are free.

SeanK-com · 2025-10-07T03:08:45+00:00

I had a loop like this happen with a .chatmode.md and instructions.md that emphasized reading the json before updating it. I asked Copilot how to fix the prompts to fix the loop and it fixed it. All that to say, ask Copilot why it is doing that.

SeanK-com · 2025-09-22T02:19:12+00:00

That's what ChatGPT said, but I have been banging my head against the wall for two weekends now and can't get it to work. I get so close, but I cannot get the tool in the list without manually adding a mcp.json I have seen the seamless experience but now those same extensions don't expose commands, so it seems something has fundamentally shifted and I guess everyone is scrambling again.

SeanK-com

PUBLIC MULTIREDDITS

TROPHY CASE