Open
Conversation
Add standardized schema for capturing project context that workers need to understand any project. Includes templates for core files (overview, architecture, domain) and recommended files (decisions, stakeholders). JSON schema enables validation. Example context created for distributed-tracking project demonstrates the schema in practice. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add new worker to discover, maintain, and audit project context: - worker.yaml with CodeWorker definition - discover skill: extract context from repos or conversation - audit skill: check freshness and completeness - update skill: update specific context files Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add registry.yaml documenting context needs for all worker types - Document CodeWorker, ContentWorker, SocialWorker, ResearchWorker, OpsWorker, and AssistantWorker context requirements - Support individual worker overrides (architect, security-scanner, context-manager) - Add README.md explaining how to declare needs for new workers - Define schema for type defaults, individual overrides, and external context references Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add new Step 5 to /prd command that offers project context population after PRD creation. Users can choose from: - Manual: Create empty templates for user to fill - Automatic: Extract context from target repo docs - Conversational: Interview user about the project - Skip: Proceed without context (with warning) This enables workers to understand projects deeply, not just track tasks. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add new Section 5 "Context Needs" to Interactive Setup - Add context_needs field to worker.yaml template - Add "Update Context Needs Registry" section for worker-specific overrides - Links to knowledge/context-needs/ for reference Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add detailed repo analysis implementation to the discover skill: - Step-by-step process for locating and analyzing repos - Source extraction tables for README, package.json, configs - Mapping rules from sources to context file sections - Draft generation and user review workflow - Incremental update mode (--update flag) documentation Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
After PRD completion, /run-project now triggers context-manager audit skill to check project context for staleness. This ensures context stays current as the codebase evolves during PRD execution. - Adds step 8c to project completion flow - Spawns context-manager audit skill after aggregating learnings - Logs audit results to progress.txt - Suggests context discovery if no context exists Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add comprehensive interview flow to context-manager discover skill: - 9 batched questions grouped by section (Overview, Architecture, Domain) - Support for pasting existing docs with extraction rules by doc type - Hybrid mode allowing automatic analysis mid-interview - Source attribution in frontmatter tracking interview details Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Create learnings.md template with sections: Patterns, Gotchas, Tips, Open Questions - Add learn skill to context-manager worker for appending insights - Define learning entry format: ### [Date] [Worker] [Task]: Title - Support category tagging for filtering: pattern, gotcha, tip, question, etc. - Add learnings_added metric to worker reporting Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
All 9 user stories verified complete: - US-001: Project context schema with templates - US-002: Context-manager worker with 4 skills - US-003: Worker context needs registry - US-004: Context discovery in /prd command - US-005: Context needs capture in /newworker - US-006: Repo analysis discovery skill - US-007: Staleness detection and post-PRD audit trigger - US-008: Conversational discovery mode - US-009: Learnings accumulation Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Two issues fixed: 1. Completion detection now recognizes both formats: - `passes: true` (old format) - `status: "completed"` (new format used by Claude sessions) The orchestrator was infinitely looping because it only checked for `passes == true` but tasks were marked with `status: "completed"`. 2. Auto-create PR when PRD completes: - Push branch to origin - Use gh CLI to create PR with summary from PRD - Include task list in PR body - Fallback message if gh not available Both PowerShell and bash scripts updated. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
When creating PRs after PRD completion, the orchestrator now: 1. Checks for 'myfork' or 'fork' remotes 2. If found, pushes to the fork remote instead of origin 3. Extracts upstream repo URL from origin for PR target 4. Uses --repo flag with gh pr create to target upstream This allows fork-based workflows where origin points to upstream and myfork/fork points to the user's fork. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
New testing infrastructure for HQ PRs: - .claude/scripts/validate-pr.ps1: Automated validation script - Script syntax checking (PowerShell, Bash) - YAML/JSON syntax validation - Worker registry consistency - PRD file existence verification - Command file structure checks - knowledge/testing/pr-validation.md: Testing strategy docs - Automated check catalog - Functional test guidelines - Future CI integration notes Usage: .\validate-pr.ps1 -Project project-context-manager Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
New command that builds verified project understanding through: 1. Automatic repo analysis (like discover) 2. Present interpretation to user 3. Probing questions per section (purpose, architecture, domain, ops) 4. User confirms, corrects, or expands 5. Write verified context files with confidence levels Key differences from /run context-manager discover: - Interactive interview process - Human verification of AI understanding - Captures "why" not just "what" - Saves interview log for future reference - Higher confidence context files Usage: /understand-project indigo-nx --repo C:/repos/indigo-nx This is foundational for agentic success - agents that misunderstand projects produce poor results. Context alignment matters. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add /understand-project to CLAUDE.md Projects section - Add learning about interview-based discovery catching misunderstandings - Expand schema.md with discovery methods documentation: - Quick discovery via /run context-manager discover - Deep discovery via /understand-project - When to use which approach - Context in external repos documentation Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add prd.json template to Step 4 alongside README.md - Add target_repo question to discovery interview - Update completion message to show both files - Add rule emphasizing both files must be generated Execution commands (/pure-ralph, /run-project, /execute-task) require prd.json but /prd was only generating README.md. This fixes the gap. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
prd.json is a functional document that mirrors README.md content. No need to show the template to users. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Research findings for hq-installer project: - Essential deps: Node.js 18+, Claude CLI (only 2 required) - Optional: Git, gh CLI, qmd, pnpm (with graceful degradation) - Documented installer strategy with 3-tier dependency approach - Confirmed authentication flow (Claude OAuth) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Create Windows installer with: - NSIS script with MUI2 branded UI and progress indicators - Node.js detection and silent install if missing - Claude CLI detection and npm install if missing - User-selectable install location (default: AppData/Local) - Start Menu and Desktop shortcuts - Comprehensive code-signing documentation Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Create complete macOS installer package with: - build-pkg.sh script using pkgbuild/productbuild - Branded HTML UI (welcome, readme, license, conclusion pages) - preinstall script for Node.js/Claude CLI detection - postinstall script for auto-installation of dependencies - PATH configuration via ~/.zshrc and /etc/paths.d - Code signing and notarization documentation The installer detects missing Node.js 18+ and Claude CLI, downloads and installs them automatically, and configures the user's shell PATH for immediate use. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Windows NSIS: Add ClaudeAuthPage custom page after installation - Uses 'claude setup-token' command for browser OAuth - Allows skip and retry with clear messaging - Checks authentication status before prompting - macOS pkg: Update postinstall and conclusion page - Updated conclusion.html with OAuth instructions - Added authenticate-claude.sh helper script to ~/my-hq/ - Instructions for 'claude setup-token' command - Shared: Add cross-platform OAuth helper scripts - installer/shared/scripts/claude-oauth.ps1 (Windows) - installer/shared/scripts/claude-oauth.sh (macOS/Linux) Both platforms support: - Browser OAuth via 'claude setup-token' command - Skip authentication for later manual setup - Clear messaging about /login for manual auth Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Created installer/template/ with starter files: - agents.md (user profile template) - CLAUDE.md (Claude configuration) - USER-GUIDE.md (documentation) - setup.md command (setup wizard) - Directory structure for workers, projects, workspace, knowledge - Updated Windows NSIS installer: - Bundled or downloaded template from GitHub releases - Added SEC06 for npm install if package.json exists - Desktop shortcut with welcome message - Fallback to minimal structure if download fails - Updated macOS installer: - Updated build-pkg.sh with template download option - postinstall creates ~/Desktop/my-hq.app launcher bundle - run_npm_install function for template dependencies - No Git required - uses HTTPS download Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Create cross-platform terminal-based setup wizard - Windows: setup-wizard.ps1 (PowerShell) - macOS: setup-wizard.sh (Bash) - Wizard collects user profile (name, role, goals, preferences) - Writes configured agents.md with user information - Shows Getting Started guide with key commands - Supports skip at any point for manual configuration later Windows integration: - NSIS finish page launches wizard via PowerShell - Start Menu shortcut added for re-running wizard macOS integration: - Wizard auto-launches after installation completes - Desktop app "my-hq Setup Wizard.app" for re-running Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add cross-platform update checking infrastructure: - check-updates.ps1 for Windows: PowerShell script that queries GitHub releases API, compares versions, downloads and installs updates - check-updates.sh for macOS: Bash script with same functionality - Windows NSIS installer: Includes update checker, Start Menu shortcut, saves .hq-version file for tracking - macOS postinstall: Includes update checker, creates desktop .app launcher, saves .hq-version file Features: - Checks GitHub releases API for latest version - Compares semantic versions (major.minor.patch) - Shows release notes when update available - Downloads installer with user consent - Rate-limited to once-per-day checks - Preserves user data during updates Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add GitHub Pages-ready landing page with OS auto-detection, system requirements, manual installation instructions, and FAQ. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Create comprehensive testing framework for validating installers on clean machines. Includes VM setup guides, automated test scripts, edge case documentation, and test result templates. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Enable non-technical professionals to set up my-hq in under 5 minutes with zero terminal commands
Completed Tasks
Created by Pure Ralph