Implement programmer agent system and consolidate agent infrastructure

Programmer Agent System:
- Add programmer-orchestrator (Opus) for workflow coordination
- Add code-planner (Sonnet) for design and planning
- Add code-implementer (Sonnet) for writing code
- Add code-reviewer (Sonnet) for quality review
- Add /programmer command and project registration skill
- Add state files for preferences and project context

Agent Infrastructure:
- Add master-orchestrator and linux-sysadmin agents
- Restructure skills to use SKILL.md subdirectory format
- Convert workflows from markdown to YAML format
- Add commands for k8s and sysadmin domains
- Add shared state files (model-policy, autonomy-levels, system-instructions)
- Add PA memory system (decisions, preferences, projects, facts)

Cleanup:
- Remove deprecated markdown skills and workflows
- Remove crontab example (moved to workflows)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
OpenCode Test
2025-12-29 13:23:42 -08:00
parent 119d2a464e
commit 431e10b449
62 changed files with 3572 additions and 539 deletions

View File

@@ -0,0 +1,69 @@
---
name: programmer-add-project
description: Register a new project with the programmer agent system
---
# Add Project to Programmer Agent
Register a new project for context-aware code development.
## Gather Information
Collect from the user:
1. **Project path**: Absolute path to project root
2. **Project name**: Short identifier (used for filename)
3. **Description**: What the project does (1-2 sentences)
4. **Tech stack**: Languages, frameworks, databases
5. **Conventions**: Path to conventions file or brief description
## Validate
Before creating:
1. Verify the path exists: `ls <path>`
2. Check for existing project file: `~/.claude/state/programmer/projects/<name>.json`
3. Look for conventions file if path provided
## Create Project File
Write to `~/.claude/state/programmer/projects/<name>.json`:
```json
{
"path": "/absolute/path/to/project",
"description": "Description of the project",
"stack": ["language", "framework", "database"],
"conventions": "See CONTRIBUTING.md or brief description",
"recentWork": [],
"activeTodos": [],
"created": "YYYY-MM-DD"
}
```
## Output
Confirm to user:
```markdown
## Project Registered
- **Name**: project-name
- **Path**: /path/to/project
- **Stack**: language, framework
- **Config**: `~/.claude/state/programmer/projects/project-name.json`
The programmer agent will now use this context when working in this project.
```
## Example Interaction
User: "Add my inventory-api project"
Agent:
1. Ask for project path
2. Ask for description
3. Ask for tech stack
4. Look for CONTRIBUTING.md or conventions
5. Create project file
6. Confirm registration