Claude Project: Your Personalized BA Documentation Assistant

What This Builds

Instead of re-explaining your documentation standards, BRD format, user story template, and project context every time you start a Claude conversation, you set it up once in a Claude Project. After that, every conversation you open automatically knows your organization's format, your project's stakeholders, and your preferred writing style. You'll stop spending 5 minutes on setup per conversation and get consistent, on-format output every time.

Prerequisites

• Claude Pro account ($20/month at claude.ai)
• Your organization's BRD template or user story format (even just notes on what sections you use)
• Your project's stakeholder list and key context (can be rough notes)
• Comfortable using Claude for basic documentation tasks

The Concept

A Claude Project is like giving a new contractor a complete onboarding packet before they start. Without it, you'd explain your standards on every call. With it, they already know your templates, your stakeholders, your terminology, and your preferences. Every deliverable follows your format without being asked.

Think of it as a dedicated AI assistant that lives inside Claude, pre-configured for your specific role and project. You can have multiple Projects: one per client engagement, or one general BA assistant.

Build It Step by Step

Part 1: Create the Project

1. Log into claude.ai with your Pro account
2. In the left sidebar, look for "Projects" (below "New chat")
3. Click "+ New project"
4. Name it, e.g., "BA Assistant: [Client/Project Name]" or "BA Documentation Tools"
5. You'll see a project workspace with a Project instructions section at the top

What you should see: A project workspace with two areas: Project instructions (system prompt area) and a conversation starter.

Part 2: Write your Project Instructions

Click "Add instructions" in the project settings. This is where you configure your assistant's knowledge and behavior.

Copy and customize this template:

You are my Business Analysis documentation assistant. You help me create requirements documents, user stories, process maps, and stakeholder communications.

## My Documentation Standards

**User Story Format:**
"As a [specific user role], I want to [specific action or capability], so that [specific business benefit]."

**Acceptance Criteria Format:**
Given/When/Then format. Each criterion should be testable and specific. No vague words like "should," "easy," "fast," or "efficient" without quantification.

**BRD Section Structure:**
1. Executive Summary
2. Business Objectives
3. Scope (In-Scope / Out-of-Scope)
4. Stakeholders
5. Functional Requirements (numbered FR-001, FR-002...)
6. Non-Functional Requirements (NFR-001...)
7. Assumptions and Constraints
8. Open Questions

**Requirement Numbering:** FR-001 format for functional, NFR-001 for non-functional

**Writing Style:**
- Active voice, present tense
- Each requirement stands alone (no cross-references)
- Use "the system shall" for functional requirements, "the system should" for desirable but not mandatory

## My Current Project Context
[Add: Project name, objective, key stakeholders, technology environment, constraints]

## My Organization's Terms
[Add any domain-specific terminology, acronyms, or company-specific language]

Click Save instructions.

Part 3: Upload Reference Documents (Optional)

In the Project workspace, click "Add to project" → "Files". You can upload:

• Your BRD template (Word or PDF)
• Your user story template
• A past requirements document as a style reference
• A project charter or scope document

Claude will reference these files in every conversation in this project.

Part 4: Test Your Configuration

Start a new conversation within the project (click "New chat" while in the project).

Test prompt 1:

Good output: Stories in exactly your specified format, numbered AC in Given/When/Then, using your requirement numbering convention.

Test prompt 2:

Good output: Claude lists your exact section structure without you having to ask.

If the output doesn't match your format, edit the Project Instructions and retry.

Part 5: Create a "Starter" Conversation Template

Write a message you'll use at the start of most documentation sessions and save it as a note. Example:

Real Example: Sprint Documentation Session

Setup: You've configured your BA Assistant Project with your user story format, acceptance criteria template, and current project context (a finance system upgrade).

Input: Your 2-page workshop notes from a meeting about expense report approval workflows.

Starting the conversation:

Output:

• 12 user stories in FR-001 format with Given/When/Then AC
• 4 open questions with context
• 2 potential conflicts flagged with explanation

Time saved: 2.5 hours of documentation → 20 minutes of review

What to Do When It Breaks

• Output format drifts from your template → Edit Project Instructions to add a more explicit example of the format. Paste a perfect sample requirement and say "Requirements should look exactly like this example."
• Claude adds extra sections you don't want → Add to instructions: "Do not add sections not listed in the BRD structure above."
• Claude misses context between conversations → Projects maintain instructions but not conversation history across sessions. Re-paste key context at the start of new sessions, or add more context to Project Instructions.
• Uploaded files aren't being referenced → Try asking explicitly: "Based on the BRD template I uploaded, what sections should this document include?"

Variations

• Simpler version: Instead of a full Project, save a "master context prompt" in a text file and paste it at the start of every Claude Free conversation. You get 80% of the benefit with no subscription needed
• Extended version: Create separate Projects per client engagement, each with the client's specific terminology, templates, and project context

What to Do Next

• This week: Set up one Project and use it for your next documentation session
• This month: Refine the instructions based on which outputs still need heavy editing
• Advanced: Connect Claude to Confluence via API (requires IT involvement) to automatically post requirements pages without copy-paste

Advanced guide for Business Analyst professionals. Claude Projects requires a Pro subscription ($20/month).