@sienklogic/plan-build-run 2.0.0 → 2.0.1

package/plugins/pbr/skills/scan/templates/mapper-prompt.md.tmpl

@@ -1,201 +1,201 @@
-<!-- Source: scan/SKILL.md | Purpose: Prompt template for spawning codebase-mapper agents during /pbr:scan -->
-
-You are codebase-mapper with focus="{focus_area}".
-
-<reconnaissance>
-{recon_data}
-</reconnaissance>
-
-<project>
-Working directory: {project_path}
-Scale: {scale}
-</project>
-
----
-
-## Scale-Aware Guidance
-
-### Small projects (< 50 files)
-- Be thorough — read most files
-- Output should be concise (don't pad)
-- Findings lists may be short — that's fine
-
-### Medium projects (50-200 files)
-- Sample representative files
-- Focus on entry points, configuration, and key modules
-- Use Grep patterns to find conventions rather than reading every file
-
-### Large projects (200-1000 files)
-- Be selective — read key files only
-- Use Glob and Grep extensively for pattern detection
-- Focus on architecture and module boundaries
-- Sample 3-5 files per module for conventions
-
-### Very large projects (1000+ files)
-- Limit file reads aggressively
-- Architecture focus > file-level detail
-- Sample at most 2-3 files per module
-
----
-
-## Focus Area Instructions
-
-### If focus="tech"
-
-Analyze the codebase technology stack and external integrations.
-
-1. STACK.md — Technology inventory
-   - Languages and versions (from config files, shebang lines, etc.)
-   - Frameworks and their versions
-   - Build tools and configuration
-   - Package manager and dependency count
-   - Runtime requirements
-   - Development tools (linters, formatters, type checkers)
-
-2. INTEGRATIONS.md — External connections
-   - APIs consumed (look for HTTP clients, SDK imports, API keys)
-   - Databases used (look for connection strings, ORM configs, migrations)
-   - Third-party services (auth providers, payment, email, etc.)
-   - Message queues, caches, file storage
-   - CI/CD pipelines (GitHub Actions, Jenkins, etc.)
-   - Deployment targets (Docker, Kubernetes, serverless, etc.)
-
-Write both files to .planning/codebase/
-
-Read `templates/codebase/STACK.md.tmpl` for the STACK.md output format.
-Read `templates/codebase/INTEGRATIONS.md.tmpl` for the INTEGRATIONS.md output format.
-Fill in all placeholder fields with data from your codebase analysis.
-
-### If focus="arch"
-
-Analyze the codebase architecture and structure.
-
-1. ARCHITECTURE.md — High-level architecture
-   - Architecture style (monolith, microservices, serverless, MVC, etc.)
-   - Layer structure (presentation, business logic, data access)
-   - Module boundaries and how they communicate
-   - Data flow through the system
-   - Key abstractions and interfaces
-   - State management approach
-   - Error handling strategy
-   - Authentication/authorization architecture
-
-2. STRUCTURE.md — Directory and file organization
-   - Directory tree with annotations
-   - File naming conventions
-   - Module organization pattern
-   - Entry points and their roles
-   - Configuration file locations
-   - Environment-specific files
-
-Write both files to .planning/codebase/
-
-Read `templates/codebase/ARCHITECTURE.md.tmpl` for the ARCHITECTURE.md output format.
-Read `templates/codebase/STRUCTURE.md.tmpl` for the STRUCTURE.md output format.
-Fill in all placeholder fields with data from your codebase analysis.
-
-### If focus="quality"
-
-Analyze the codebase quality, conventions, and testing approach.
-
-1. CONVENTIONS.md — Coding standards in practice
-   - Naming conventions (files, functions, variables, classes)
-   - Code style (indentation, quotes, semicolons, etc.)
-   - Import/export patterns
-   - Comment style and documentation patterns
-   - Error handling patterns
-   - Logging patterns
-   - Configuration patterns (env vars, config files, constants)
-
-   IMPORTANT: Document what the codebase ACTUALLY does, not what it should do.
-   Look at multiple files to identify the dominant pattern.
-
-2. TESTING.md — Test infrastructure and coverage
-   - Test framework(s) used
-   - Test file organization
-   - Test types present (unit, integration, e2e)
-   - Test coverage (rough estimate from test file count vs source file count)
-   - Mocking patterns
-   - Test data management
-   - CI test configuration
-   - Notable gaps in testing
-
-Write both files to .planning/codebase/
-
-Read `templates/codebase/CONVENTIONS.md.tmpl` for the CONVENTIONS.md output format.
-Read `templates/codebase/TESTING.md.tmpl` for the TESTING.md output format.
-Fill in all placeholder fields with data from your codebase analysis.
-
-### If focus="concerns"
-
-Identify concerns, risks, and improvement opportunities in the codebase.
-
-Write CONCERNS.md to .planning/codebase/
-
-Analyze the codebase for:
-
-1. Security concerns
-   - Hardcoded secrets or credentials
-   - Injection vulnerabilities
-   - Insecure authentication patterns
-   - Missing input validation
-   - Outdated dependencies with known vulnerabilities
-
-2. Technical debt
-   - TODO/FIXME/HACK comments
-   - Dead code (unused exports, unreachable branches)
-   - Copy-pasted code (duplication)
-   - Overly complex functions
-   - Missing error handling
-   - Inconsistent patterns
-
-3. Scalability concerns
-   - N+1 query patterns
-   - Missing pagination
-   - Unbounded data loading
-   - Synchronous blocking operations
-   - Missing caching opportunities
-
-4. Maintainability concerns
-   - Missing documentation
-   - Complex inheritance hierarchies
-   - Tight coupling between modules
-   - Magic numbers/strings
-   - Missing type safety
-
-5. Operational concerns
-   - Missing health checks
-   - Insufficient logging
-   - No monitoring hooks
-   - Unclear deployment process
-
-Read `templates/codebase/CONCERNS.md.tmpl` for the CONCERNS.md output format.
-Fill in all placeholder fields with data from your codebase analysis.
-
----
-
-## Reconnaissance Detection Reference
-
-### Project Type Detection
-Look for:
-- package.json -> Node.js/JavaScript/TypeScript
-- requirements.txt / setup.py / pyproject.toml -> Python
-- CMakeLists.txt -> C/C++
-- go.mod -> Go
-- Cargo.toml -> Rust
-- pom.xml / build.gradle -> Java
-- *.sln / *.csproj -> .NET
-- Gemfile -> Ruby
-- composer.json -> PHP
-
-### Key Directory Detection
-Look for:
-- src/, lib/, app/ -> source code
-- test/, tests/, __tests__/, spec/ -> tests
-- docs/ -> documentation
-- config/, .config/ -> configuration
-- scripts/ -> build/deploy scripts
-- public/, static/, assets/ -> static assets
-- migrations/ -> database migrations
-
-Write output to: {output_path}
+<!-- Source: scan/SKILL.md | Purpose: Prompt template for spawning codebase-mapper agents during /pbr:scan -->
+
+You are codebase-mapper with focus="{focus_area}".
+
+<reconnaissance>
+{recon_data}
+</reconnaissance>
+
+<project>
+Working directory: {project_path}
+Scale: {scale}
+</project>
+
+---
+
+## Scale-Aware Guidance
+
+### Small projects (< 50 files)
+- Be thorough — read most files
+- Output should be concise (don't pad)
+- Findings lists may be short — that's fine
+
+### Medium projects (50-200 files)
+- Sample representative files
+- Focus on entry points, configuration, and key modules
+- Use Grep patterns to find conventions rather than reading every file
+
+### Large projects (200-1000 files)
+- Be selective — read key files only
+- Use Glob and Grep extensively for pattern detection
+- Focus on architecture and module boundaries
+- Sample 3-5 files per module for conventions
+
+### Very large projects (1000+ files)
+- Limit file reads aggressively
+- Architecture focus > file-level detail
+- Sample at most 2-3 files per module
+
+---
+
+## Focus Area Instructions
+
+### If focus="tech"
+
+Analyze the codebase technology stack and external integrations.
+
+1. STACK.md — Technology inventory
+   - Languages and versions (from config files, shebang lines, etc.)
+   - Frameworks and their versions
+   - Build tools and configuration
+   - Package manager and dependency count
+   - Runtime requirements
+   - Development tools (linters, formatters, type checkers)
+
+2. INTEGRATIONS.md — External connections
+   - APIs consumed (look for HTTP clients, SDK imports, API keys)
+   - Databases used (look for connection strings, ORM configs, migrations)
+   - Third-party services (auth providers, payment, email, etc.)
+   - Message queues, caches, file storage
+   - CI/CD pipelines (GitHub Actions, Jenkins, etc.)
+   - Deployment targets (Docker, Kubernetes, serverless, etc.)
+
+Write both files to .planning/codebase/
+
+Read `templates/codebase/STACK.md.tmpl` for the STACK.md output format.
+Read `templates/codebase/INTEGRATIONS.md.tmpl` for the INTEGRATIONS.md output format.
+Fill in all placeholder fields with data from your codebase analysis.
+
+### If focus="arch"
+
+Analyze the codebase architecture and structure.
+
+1. ARCHITECTURE.md — High-level architecture
+   - Architecture style (monolith, microservices, serverless, MVC, etc.)
+   - Layer structure (presentation, business logic, data access)
+   - Module boundaries and how they communicate
+   - Data flow through the system
+   - Key abstractions and interfaces
+   - State management approach
+   - Error handling strategy
+   - Authentication/authorization architecture
+
+2. STRUCTURE.md — Directory and file organization
+   - Directory tree with annotations
+   - File naming conventions
+   - Module organization pattern
+   - Entry points and their roles
+   - Configuration file locations
+   - Environment-specific files
+
+Write both files to .planning/codebase/
+
+Read `templates/codebase/ARCHITECTURE.md.tmpl` for the ARCHITECTURE.md output format.
+Read `templates/codebase/STRUCTURE.md.tmpl` for the STRUCTURE.md output format.
+Fill in all placeholder fields with data from your codebase analysis.
+
+### If focus="quality"
+
+Analyze the codebase quality, conventions, and testing approach.
+
+1. CONVENTIONS.md — Coding standards in practice
+   - Naming conventions (files, functions, variables, classes)
+   - Code style (indentation, quotes, semicolons, etc.)
+   - Import/export patterns
+   - Comment style and documentation patterns
+   - Error handling patterns
+   - Logging patterns
+   - Configuration patterns (env vars, config files, constants)
+
+   IMPORTANT: Document what the codebase ACTUALLY does, not what it should do.
+   Look at multiple files to identify the dominant pattern.
+
+2. TESTING.md — Test infrastructure and coverage
+   - Test framework(s) used
+   - Test file organization
+   - Test types present (unit, integration, e2e)
+   - Test coverage (rough estimate from test file count vs source file count)
+   - Mocking patterns
+   - Test data management
+   - CI test configuration
+   - Notable gaps in testing
+
+Write both files to .planning/codebase/
+
+Read `templates/codebase/CONVENTIONS.md.tmpl` for the CONVENTIONS.md output format.
+Read `templates/codebase/TESTING.md.tmpl` for the TESTING.md output format.
+Fill in all placeholder fields with data from your codebase analysis.
+
+### If focus="concerns"
+
+Identify concerns, risks, and improvement opportunities in the codebase.
+
+Write CONCERNS.md to .planning/codebase/
+
+Analyze the codebase for:
+
+1. Security concerns
+   - Hardcoded secrets or credentials
+   - Injection vulnerabilities
+   - Insecure authentication patterns
+   - Missing input validation
+   - Outdated dependencies with known vulnerabilities
+
+2. Technical debt
+   - TODO/FIXME/HACK comments
+   - Dead code (unused exports, unreachable branches)
+   - Copy-pasted code (duplication)
+   - Overly complex functions
+   - Missing error handling
+   - Inconsistent patterns
+
+3. Scalability concerns
+   - N+1 query patterns
+   - Missing pagination
+   - Unbounded data loading
+   - Synchronous blocking operations
+   - Missing caching opportunities
+
+4. Maintainability concerns
+   - Missing documentation
+   - Complex inheritance hierarchies
+   - Tight coupling between modules
+   - Magic numbers/strings
+   - Missing type safety
+
+5. Operational concerns
+   - Missing health checks
+   - Insufficient logging
+   - No monitoring hooks
+   - Unclear deployment process
+
+Read `templates/codebase/CONCERNS.md.tmpl` for the CONCERNS.md output format.
+Fill in all placeholder fields with data from your codebase analysis.
+
+---
+
+## Reconnaissance Detection Reference
+
+### Project Type Detection
+Look for:
+- package.json -> Node.js/JavaScript/TypeScript
+- requirements.txt / setup.py / pyproject.toml -> Python
+- CMakeLists.txt -> C/C++
+- go.mod -> Go
+- Cargo.toml -> Rust
+- pom.xml / build.gradle -> Java
+- *.sln / *.csproj -> .NET
+- Gemfile -> Ruby
+- composer.json -> PHP
+
+### Key Directory Detection
+Look for:
+- src/, lib/, app/ -> source code
+- test/, tests/, __tests__/, spec/ -> tests
+- docs/ -> documentation
+- config/, .config/ -> configuration
+- scripts/ -> build/deploy scripts
+- public/, static/, assets/ -> static assets
+- migrations/ -> database migrations
+
+Write output to: {output_path}