User Stories by Persona¶

This page organizes all Code Scalpel tool use cases by user persona, helping you quickly find relevant workflows for your role.

Quick Navigation¶

• 👤 Sarah (AI User) - Cost reduction, fast setup
• 🔰 Alex (First-Timer) - Learning, getting started
• 🛡️ Marcus (Security Engineer) - AppSec, compliance
• 👥 David (Team Lead) - Team rollout, ROI
• 🏢 Jennifer (Enterprise Architect) - Scale, governance
• 🔧 Chris (OSS Contributor) - Architecture, integration

👤 Sarah (AI User)¶

Goal: Reduce AI costs and improve code quality without complex setup

Cost Reduction Stories¶

Code Quality Stories¶

Setup Stories¶

🔰 Alex (First-Timer)¶

Goal: Understand what Code Scalpel does in 10 seconds and get hands-on experience

Learning Stories¶

Exploration Stories¶

🛡️ Marcus (Security Engineer)¶

Goal: Find real vulnerabilities with <10% false positive rate, map to OWASP Top 10

Vulnerability Detection Stories¶

Dependency Security Stories¶

Compliance Stories¶

👥 David (Team Lead)¶

Goal: Roll out Code Scalpel to 10-person team in <1 hour, demonstrate ROI

Team Onboarding Stories¶

Code Review Stories¶

Project Understanding Stories¶

ROI Demonstration Stories¶

🏢 Jennifer (Enterprise Architect)¶

Goal: Deploy to 500-2000 users with SOC2/ISO 27001 compliance, governance controls

Governance Stories¶

Scale Stories¶

Compliance Reporting Stories¶

Multi-Team Stories¶

🔧 Chris (OSS Contributor)¶

Goal: Understand architecture, contribute features, integrate with other tools

Architecture Understanding Stories¶

Contribution Stories¶

Integration Stories¶

Testing Stories¶

Cross-Persona Workflows¶

Some workflows span multiple personas:

Code Quality Workflow (Everyone)¶

1. analyze_code - Understand structure
2. security_scan - Find vulnerabilities
3. simulate_refactor - Verify fixes
4. generate_unit_tests - Add test coverage

Onboarding Workflow (Alex → David → Jennifer)¶

1. get_project_map - Project overview
2. crawl_project - File inventory
3. get_call_graph - Execution flow
4. get_cross_file_dependencies - Dependency understanding

Security Audit Workflow (Marcus → Jennifer)¶

1. scan_dependencies - CVE check
2. security_scan - Code vulnerabilities
3. cross_file_security_scan - Multi-file taint
4. code_policy_check - Compliance verification
5. verify_policy_integrity - Policy integrity check

Tool Categories by Use Case¶

🚀 Getting Started (First 5 minutes)¶

1. analyze_code - See structure
2. extract_code - Get specific code
3. get_file_context - Quick overview

💰 Cost Optimization (Sarah's priorities)¶

1. extract_code - 200x token reduction
2. get_file_context - Check before reading
3. get_symbol_references - Precise search

🛡️ Security (Marcus's priorities)¶

1. security_scan - OWASP Top 10
2. cross_file_security_scan - Multi-file taint
3. scan_dependencies - CVE detection
4. unified_sink_detect - Polyglot sinks

🏢 Enterprise (Jennifer's priorities)¶

1. code_policy_check - Compliance automation
2. verify_policy_integrity - Policy verification
3. validate_paths - Access control

🔍 Code Understanding (Everyone)¶

1. get_project_map - Architecture view
2. get_call_graph - Execution flow
3. get_cross_file_dependencies - Dependency tracing
4. crawl_project - File inventory

Related Documentation¶

• Tools Index - Complete tool reference
• API Reference - Detailed API documentation
• Getting Started - First-time setup
• Persona Documentation Audit - Comprehensive persona analysis