Non-engineering use case: PM running entire practice through Claude Code (200+ commits, 0 code)

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Claude Code's onboarding, docs, and examples are entirely oriented toward software engineering. Non-engineering knowledge workers (PMs, analysts, researchers) who could benefit from the core primitive (CLAUDE.md, persistent context, git integration, tool use) have no entry point or guidance.

Proposed Solution

I've been running my entire PMdomain through Claude Code at a large tech firm. 200+ commits in 2 weeks, 73% co-authored with Claude, zero lines of application code. Version-controlled decisions, narrative traceability across strategy docs, multi-PM collaboration via PRs and CODEOWNERS. Happy to do a walkthrough with the team or share sanitized patterns if useful.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Documentation

Use Case Example

A PM uses a git repo as their workspace. CLAUDE.md encodes their thinking framework, not coding standards. Product artifacts (PRDs, decision logs, evidence files) have lifecycle states managed through commits. Decisions get numbered IDs and are resolved or reverted with commit rationale. Multiple PMs collaborate through PRs with domain-scoped ownership.

Additional Context

Why I'm posting this

I think the primitives Claude Code is built on (persistent context, file system as workspace, CLAUDE.md, git integration, tool use) are more general than the current positioning suggests. I've built a few things on top of them that I think would be interesting to the team here.

Happy to do a walkthrough or share more if anyone's curious. Also open to writing this up more formally if it would be useful.