Claude reviews code across six dimensions — correctness, security, performance, readability, test coverage, and edge cases — consistently, every time. This post shows the exact prompts, a worked example with three real bugs, and an honest list of what Claude cannot do.

Finding a gap in your test cases during QA is expensive. This post shows how to use Claude to cross-check test cases against your FRD, surface redundant coverage, and generate the missing tests before QA finds them.

Every time you start a Claude Code session without a CLAUDE.md file, you are starting from zero. This post shows what CLAUDE.md is, the 10 sections it should have, and the full ClientHub example you can copy.

Test cases written from memory miss things. This post shows how to use Claude to generate a complete, importable test case set from your FRD — covering positive, negative, edge case, and role-based scenarios.

The FRD already has everything Jira needs. This post shows how to use Claude to generate epics, stories, and tasks top-down — and push them directly to Jira via the MCP without touching the interface.

Claude can generate Confluence-ready wiki markup directly from your BRD and FRD — and with the Atlassian MCP connected, push the pages to your Confluence space without you touching a browser.

Clients don't read BRDs. This post shows how to use Claude to create a client-friendly project summary, run a design review checklist, handle change requests cleanly, and get a formal sign-off — all for ClientHub.

You have a BRD. You have an FRD. But are these two documents actually talking about the same project? This post shows how to use Claude to cross-check your documents, generate a traceability matrix, and fix gaps before they reach development.

If the BRD is the "what," the FRD is the "how." This post shows how to write a Functional Requirements Document using Claude Code — continuing with the ClientHub project from Post 1.

I used to dread writing BRDs. Not because the thinking was hard — I know…