@pennyfarthing/core 9.2.0 → 9.3.0

package/pennyfarthing-dist/workflows/project-setup/steps/step-03-repos-yaml.md

@@ -1,159 +0,0 @@
-# Step 3: Generate repos.yaml
-
-<purpose>
-Generate the repos.yaml configuration file based on discovered project structure, with user refinement.
-</purpose>
-
-<instructions>
-1. Transform discovery data into repos.yaml format
-2. Present draft configuration to user
-3. Allow user to edit/refine entries
-4. Write finalized repos.yaml to project root
-</instructions>
-
-<output>
-- repos.yaml file created at project root
-- All repositories properly configured
-- Commands and metadata accurate
-- User has approved the configuration
-</output>
-
-## REPOS.YAML STRUCTURE
-
-```yaml
-# Repository Configuration for {project_name}
-# Generated by Pennyfarthing project-setup workflow
-
-repos:
-  {repo_key}:
-    path: {relative_path}           # Path from project root
-    type: {api|ui|cli|library|orchestrator|framework}
-    description: {brief_description}
-    language: {typescript|python|rust|go|java}
-
-    # Commands (optional - omit if not applicable)
-    test_command: {command}
-    build_command: {command}
-    lint_command: {command}
-    dev_command: {command}
-
-    # Additional metadata (optional)
-    framework: {express|react|fastapi|etc}
-    notes: |
-      Any special notes about this repo.
-
-# Architecture notes:
-# Add any project-wide architectural notes here
-```
-
-## GENERATION RULES
-
-### Repo Keys
-- Use lowercase, descriptive names
-- For monorepos: use package names (`api`, `ui`, `shared`)
-- For orchestrators: use `orchestrator` for root, repo names for subrepos
-
-### Path Rules
-- Root repo: use `.`
-- Subrepos: use relative path from project root
-- Monorepo packages: use package path (`packages/api`)
-
-### Type Classification
-
-| Type | When to Use |
-|------|-------------|
-| `orchestrator` | Root of multi-repo project with sprint/ |
-| `api` | Backend service, REST/GraphQL endpoints |
-| `ui` | Frontend application |
-| `cli` | Command-line tool |
-| `library` | Shared code, npm package |
-| `framework` | Distributable framework (like pennyfarthing) |
-
-### Command Extraction
-
-Extract from discovered package.json scripts:
-```javascript
-{
-  "scripts": {
-    "test": "jest",      // → test_command: npm test
-    "build": "tsc",      // → build_command: npm run build
-    "lint": "eslint",    // → lint_command: npm run lint
-    "dev": "nodemon"     // → dev_command: npm run dev
-  }
-}
-```
-
-## INTERACTIVE REFINEMENT
-
-Present the generated repos.yaml and ask:
-
-```
-📄 Generated repos.yaml
-════════════════════════
-
-{yaml_content}
-
-Options:
-[A] Accept and write to {output_repos}
-[E] Edit a specific repo entry
-[N] Add a new repo entry
-[D] Delete a repo entry
-[P] Preview in different format
-```
-
-### Edit Flow
-If user selects [E]:
-1. List repo keys
-2. Ask which to edit
-3. Show current values
-4. Accept new values
-5. Return to main menu
-
-## EXAMPLE OUTPUT
-
-For a typical api+ui project:
-
-```yaml
-# Repository Configuration for my-project
-# Generated by Pennyfarthing project-setup workflow
-
-repos:
-  orchestrator:
-    path: .
-    type: orchestrator
-    description: Project coordination and sprint management
-    language: javascript
-
-  api:
-    path: my-project-api
-    type: api
-    description: Backend REST API
-    language: typescript
-    framework: express
-    test_command: npm test
-    build_command: npm run build
-    lint_command: npm run lint
-
-  ui:
-    path: my-project-ui
-    type: ui
-    description: React frontend application
-    language: typescript
-    framework: react
-    test_command: npm test
-    build_command: npm run build
-    lint_command: npm run lint
-    dev_command: npm run dev
-```
-
-## SUCCESS CRITERIA
-
-✅ repos.yaml accurately reflects project structure
-✅ All detected repos included
-✅ Commands verified and correct
-✅ User has reviewed and approved
-✅ File written to project root
-
-## NEXT STEP
-
-After repos.yaml is written and approved, proceed to `step-04-claude-md.md` to generate the CLAUDE.md file.

package/pennyfarthing-dist/workflows/project-setup/steps/step-04-claude-md.md

@@ -1,186 +0,0 @@
-# Step 4: Generate CLAUDE.md
-
-<purpose>
-Generate the project's CLAUDE.md file - the primary instruction file that Claude Code reads on every session. This file defines project-specific rules, structure, and workflows.
-</purpose>
-
-<instructions>
-1. Analyze repos.yaml and discovered tech stack
-2. Generate CLAUDE.md with project-specific content
-3. Include correct commands, structure, and workflows
-4. Allow user to review and refine
-5. Write to project root
-</instructions>
-
-<output>
-- CLAUDE.md file created at project root
-- Accurate project structure documented
-- Correct build/test/lint commands
-- Appropriate workflow guidance
-- User has approved the content
-</output>
-
-## CLAUDE.MD STRUCTURE
-
-```markdown
-# CLAUDE.md - {Project Name}
-
-This file provides guidance to Claude Code when working on this project.
-
-## Project Overview
-
-{Brief description of what the project does}
-
-**Type:** {orchestrator|api|ui|cli|library|framework}
-**Node:** {version if applicable}
-**Type:** {ES module|CommonJS}
-
-## Repository Structure
-
-{if orchestrator}
-```
-{project_name}/              # Orchestrator
-├── .claude/                 # Claude Code configuration
-├── .pennyfarthing/          # Pennyfarthing framework
-├── sprint/                  # Sprint tracking
-├── .session/                # Active work sessions
-├── {subrepo1}/              # {description}
-└── {subrepo2}/              # {description}
-```
-{/if}
-
-{if monorepo}
-```
-{project_name}/
-├── packages/
-│   ├── {package1}/          # {description}
-│   └── {package2}/          # {description}
-├── .claude/
-└── .pennyfarthing/
-```
-{/if}
-
-{if single_repo}
-```
-{project_name}/
-├── src/                     # Source code
-├── tests/                   # Tests
-├── .claude/
-└── .pennyfarthing/
-```
-{/if}
-
-## Build Commands
-
-```bash
-{build_command}              # Build the project
-{test_command}               # Run tests
-{lint_command}               # Run linter
-{dev_command}                # Start development
-```
-
-## Development Workflow
-
-{if has_sprint}
-- `/sm` - Scrum Master (story management)
-- `/tea` - Test Engineer/Architect
-- `/dev` - Developer
-- `/reviewer` - Code Reviewer
-{/if}
-
-## Git Workflow
-
-- **Feature branches:** `feat/{story}-{description}`
-- **Bug fixes:** `fix/{issue}-{description}`
-- **PRs target:** `develop` (or `main` if no develop)
-
-## Testing
-
-```bash
-{test_command}                        # Run all tests
-{test_command} -- --grep "pattern"    # Run specific tests
-```
-
-## Important Notes
-
-{Project-specific notes, gotchas, conventions}
-```
-
-## GENERATION LOGIC
-
-### 1. Extract from repos.yaml
-
-Read the repos.yaml created in step 2:
-- Project name from orchestrator/root repo
-- Type from repo classification
-- Commands from each repo
-
-### 2. Detect Additional Context
-
-Scan for:
-- `tsconfig.json` → TypeScript config details
-- `jest.config.*` → Test framework config
-- `.eslintrc.*` → Linting config
-- `Dockerfile` → Container info
-- CI config (`.github/workflows/`, `.gitlab-ci.yml`)
-
-### 3. Include Pennyfarthing Integration
-
-If sprint/ exists:
-```markdown
-## Sprint Management
-
-- `/sprint status` - View current sprint
-- `/sprint backlog` - Available stories
-- `/sprint work` - Start a story
-```
-
-### 4. Add Project-Specific Sections
-
-Based on tech stack:
-
-**For TypeScript projects:**
-```markdown
-## TypeScript
-
-- Use `.js` extensions in imports
-- Strict mode enabled
-- ES modules (`"type": "module"`)
-```
-
-**For React projects:**
-```markdown
-## React Patterns
-
-- Functional components with hooks
-- Component files in `src/components/`
-- Tests co-located with components
-```
-
-## INTERACTIVE REFINEMENT
-
-```
-📄 Generated CLAUDE.md
-═══════════════════════
-
-{preview of generated content}
-
-Options:
-[A] Accept and write to CLAUDE.md
-[E] Edit a section
-[S] Add a new section
-[R] Regenerate with different focus
-[P] Preview full content
-```
-
-## SUCCESS CRITERIA
-
-✅ CLAUDE.md accurately describes project
-✅ Commands are correct and tested
-✅ Structure matches actual project
-✅ Workflows appropriate for project type
-✅ User has reviewed and approved
-
-## NEXT STEP
-
-After CLAUDE.md is written, proceed to `step-05-shared-context.md` to populate the shared-context.md file.

package/pennyfarthing-dist/workflows/project-setup/steps/step-05-shared-context.md

@@ -1,185 +0,0 @@
-# Step 5: Populate shared-context.md
-
-<purpose>
-Populate the shared-context.md file with accurate project information based on discovery and repos.yaml. This file is loaded by all agents.
-</purpose>
-
-<instructions>
-1. Read template from .claude/project/docs/shared-context.md
-2. Replace placeholder content with discovered information
-3. Add repo-specific sections for each repository
-4. Include accurate commands and workflows
-5. Allow user to review and refine
-</instructions>
-
-<output>
-- shared-context.md populated with real project data
-- Tech stack section accurate
-- Repo structure matches repos.yaml
-- Commands verified correct
-- User has approved content
-</output>
-
-## SHARED-CONTEXT STRUCTURE
-
-The shared-context.md has these key sections to populate:
-
-### 1. Project Section
-
-```markdown
-## Project
-
-- **Name:** {from repos.yaml or detection}
-- **Sprint Status:** `sprint/current-sprint.yaml`
-- **Active Work:** `.session/{story-id}-session.md`
-- **Agent Framework:** Pennyfarthing (npm)
-```
-
-### 2. Tech Stack Table
-
-Generate from repos.yaml:
-
-```markdown
-### Tech Stack
-
-| Component | Language | Framework | Notes |
-|-----------|----------|-----------|-------|
-| API       | TypeScript | Express | REST endpoints |
-| UI        | TypeScript | React   | Vite build |
-| Shared    | TypeScript | -       | Common types |
-```
-
-### 3. Repo Structure
-
-For orchestrator pattern:
-```markdown
-### Repo Structure
-
-```
-{project}/                   # Orchestrator
-├── .claude/                 # Claude Code configuration
-├── .pennyfarthing/          # Pennyfarthing framework
-├── sprint/                  # Sprint tracking
-├── .session/                # Active work sessions
-├── {project}-api/           # API subrepo (gitignored, clone separately)
-│   ├── src/
-│   └── tests/
-└── {project}-ui/            # UI subrepo (gitignored, clone separately)
-    ├── src/
-    └── public/
-```
-```
-
-For monorepo:
-```markdown
-### Repo Structure
-
-```
-{project}/
-├── packages/
-│   ├── api/                 # Backend service
-│   ├── ui/                  # Frontend app
-│   └── shared/              # Common code
-├── .claude/
-└── .pennyfarthing/
-```
-```
-
-### 4. Git Branch Strategy
-
-```markdown
-## Git Branch Strategy
-
-- **All work:** Feature branches
-- **Branch from:** `develop` (or `main` if no develop)
-- **PRs target:** `develop`
-- **Naming:** `feat/{story}-{description}` or `fix/{issue}-{description}`
-```
-
-### 5. Testing Commands
-
-Extract from repos.yaml and format:
-
-```markdown
-## Testing Commands
-
-{if orchestrator with subrepos}
-### API
-```bash
-cd {project}-api && npm test
-```
-
-### UI
-```bash
-cd {project}-ui && npm test
-```
-{/if}
-
-{if monorepo}
-```bash
-# Run all tests
-pnpm test
-
-# Run specific package
-pnpm test --filter @{project}/api
-```
-{/if}
-
-{if single repo}
-```bash
-{test_command}
-{test_command} -- --grep "pattern"
-```
-{/if}
-```
-
-### 6. Building
-
-```markdown
-## Building
-
-{per-repo build commands from repos.yaml}
-```
-
-## POPULATION LOGIC
-
-1. **Read existing file** - preserve any user customizations
-2. **Identify placeholder sections** - look for template markers
-3. **Replace with real data** - from repos.yaml and discovery
-4. **Preserve custom sections** - don't overwrite user additions
-5. **Add new sections** - for repos not in template
-
-## INTERACTIVE REFINEMENT
-
-```
-📄 Updated shared-context.md
-═════════════════════════════
-
-Sections updated:
-  ✓ Project name and metadata
-  ✓ Tech stack table ({n} components)
-  ✓ Repo structure diagram
-  ✓ Testing commands
-  ✓ Build commands
-
-Preview of changes:
-{diff or summary}
-
-Options:
-[A] Accept and write changes
-[E] Edit a specific section
-[V] View full file
-[D] Show diff from original
-```
-
-## SUCCESS CRITERIA
-
-✅ All placeholder content replaced
-✅ Tech stack matches actual project
-✅ Commands are accurate and tested
-✅ Repo structure reflects reality
-✅ User has reviewed and approved
-
-## NEXT STEP
-
-After shared-context.md is updated, proceed to `step-06-task-runner.md` to create justfile/makefile for orchestrator command proxying.