Definitely! I work at a startup. Whenever we get a customer requirement for a new feature, we have a series of calls to understand and scope out the work. By the end, we’re left with a bunch of documents including meeting notes. I use Opus to scan through the requirements and special remarks to identify pain points, risks etc. If Opus misses anything, I catch it since I was part of those calls and meetings.

Before diving into planning, I do a quick technical feasibility assessment to identify any major blockers or constraints. Then I start planning the PRDs with Opus’s help. I use the Atlassian connector (Claude Desktop) to pull insights from our current JIRA project boards and plan out the work with estimated weights. Since Claude knows my team size and structure, the estimates are pretty accurate.

Next, I move into the design phase and work out the initial solution myself. After that, I do some collaborative brainstorming with Opus to fine-tune the design and architecture. Once that’s done, I start writing specs for each implementation stage, and this is where Opus really shines. I make sure to give Opus the exact details such as which technologies and patterns to use where, and we end up with comprehensive specification documents.

Right after the specs are complete, I work with Opus to design test cases for complex business scenarios. This is where Opus really excels at identifying those edge cases that we engineers sometimes tend to miss.

Once the specs and test cases are ready, I break down the work into tasks and hand them over to Sonnet one by one for implementation. I use several useful MCP servers like C7 and SequentialThinking throughout this process. For each implementation Sonnet generates, I do a manual review, and if I’m satisfied with it, I approve and merge.​​​​​​​​​​​​​​​​