CC
0 XP
0

Chapter 4: Beyond Code

Team & Cross-Functional Workflows

concept5 min

Team & Cross-Functional Workflows

Claude Code gets even more powerful when your whole team uses it — not just engineers.

💡Info

When everyone on the team uses Claude Code with shared context files, the AI becomes a team member that knows your product, your conventions, and your goals.

Shared CLAUDE.md for Teams

Create a CLAUDE.md that the whole team can use:

# CLAUDE.md
 
Acme Corp — B2B SaaS for inventory management.
 
## Product
- ICP: Mid-market retailers (50-500 employees)
- Key differentiator: Real-time sync across locations
- Current focus: Mobile app launch (Q2 2026)
 
## Brand Voice
- Professional but approachable
- Data-driven — always cite numbers
- Never use: "synergy", "leverage", "game-changer"
 
## Team
- Product: Use /docs/prd-template.md for specs
- Marketing: Style guide at /content/style-guide.md
- Engineering: See /src/ for codebase conventions
✅Tip

Commit this to your repo. Everyone on the team gets the same context when they run Claude Code — consistent output across roles.

Marketing + Engineering

Bridge the gap between marketing and engineering:

"Read the changelog in CHANGELOG.md and write release notes for our customers. Focus on benefits, not technical details."

"Turn this PRD at docs/notification-prefs.md into a customer-facing blog post announcing the feature."

"Read the landing page at src/app/page.tsx and suggest copy improvements based on our ICP in CLAUDE.md."

Product + Design

"Read the user feedback in research/interviews/ and create a prioritized feature list. Map each to a user pain point."

"Review the wireframes described in docs/wireframes.md and write user stories for each screen."

Content Pipelines

Set up repeatable content workflows:

  1. Content briefs — "Read our SEO keywords in seo-keywords.csv and generate 10 blog post briefs with titles, outlines, and target word counts"
  2. Drafting — "Write the first draft of brief #3. Follow the style guide."
  3. Editing — "Read draft-3.md. Cut it by 20%, improve the intro, add a stronger CTA."
  4. Repurposing — "Turn this blog post into 5 Twitter threads, 1 LinkedIn post, and 3 email snippets."
💡Info

Each step reads from and writes to files in your project. No copy-pasting between tools. Claude Code keeps the full context across every step.

Meeting & Decision Docs

"I just pasted our meeting notes into meeting-2026-03-26.md. Extract action items, assign owners based on the team list in CLAUDE.md, and create follow-up tasks."

"Read the three proposals in /proposals/ and write a comparison table with pros, cons, effort estimate, and recommendation."

The Power Move: Custom Commands

For repeated workflows, you can create custom commands — reusable prompts saved as markdown files that run like slash commands (you built these in Chapter 2):

<!-- File: .claude/commands/content-brief.md -->
Read our SEO keywords and content calendar.
Generate a content brief with:
- Title and target keyword
- Outline (H2s and H3s)
- Target word count
- Internal links to include
- CTA recommendation
Output as a new file in /content/briefs/
✅Tip

Custom commands turn Claude Code from a one-off tool into a team workflow engine. Marketing, product, and ops can all have their own commands that encode their best practices. See Chapter 2, section 18 for how to create them.

Getting Your Team Started

  1. Install Claude Code for everyone (yes, even the non-engineers)
  2. Create a shared CLAUDE.md in your repo or shared folder
  3. Start with one workflow — pick the most repetitive task and automate it
  4. Add role-specific context — each person can have their own preferences in ~/.claude/CLAUDE.md
  5. Share what works — when someone finds a great prompt pattern, add it as a skill

Try it now

You don't need a team to try this. Here's a 3-minute exercise:

  1. Create a folder called test-content with a few text files — a meeting notes draft, a short email, a CSV with some numbers
  2. Add a simple CLAUDE.md: "I'm a product manager. Help me work with these documents."
  3. Run claude in that folder
  4. Try: "Summarize everything in this folder" or "Turn the meeting notes into action items"

Notice how the same tool you used to build an entire app works just as well on a folder of documents. The workflow is identical: context (CLAUDE.md), clear instructions, iterate.

You don't need to be a coder to be a power user of Claude Code. You just need to know what you want — and now you know how to ask for it.

PreviousNext