kazuki nakai
|
d5dfd7da21
|
refactor(docs): normalize documentation naming to lowercase for PEP8 compliance (#434)
* refactor(docs): rename directories to lowercase for PEP8 compliance
- Developer-Guide → developer-guide
- Getting-Started → getting-started
- Reference → reference
- Templates → templates
- User-Guide → user-guide
- User-Guide-jp → user-guide-jp
- User-Guide-kr → user-guide-kr
- User-Guide-zh → user-guide-zh
This change aligns with Python PEP8 package naming conventions.
All 43 files affected.
* refactor: rename root documentation files to lowercase
- CHANGELOG.md → changelog.md
- CODE_OF_CONDUCT.md → code_of_conduct.md
- CONTRIBUTING.md → contributing.md
- SECURITY.md → security.md
Aligns with Python package naming conventions (PEP8).
README files remain uppercase as per convention.
* refactor: move documentation files to docs/ for cleaner root
Moved OSS standard files to docs/:
- CHANGELOG.md → docs/CHANGELOG.md
- CODE_OF_CONDUCT.md → docs/CODE_OF_CONDUCT.md
- CONTRIBUTING.md → docs/CONTRIBUTING.md
- SECURITY.md → docs/SECURITY.md
Root now contains only essential files:
✓ README files (表紙: en, ja, kr, zh)
✓ LICENSE (法的要件)
✓ Build configs (pyproject.toml, setup.py, MANIFEST.in)
✓ VERSION
Rationale:
Cleaner root structure following modern Python project conventions.
All detailed documentation consolidated in docs/ directory.
* refactor: update documentation links after restructure
Auto-updated internal documentation links to reflect new structure:
- docs/ subdirectories now lowercase (PEP8)
- Root files moved to docs/
- All cross-references updated
This commit includes linter-generated link updates.
* chore(docs): keep OSS-standard uppercase root files (CHANGELOG, CODE_OF_CONDUCT, CONTRIBUTING, SECURITY)
* chore(docs): remove duplicated PR docs from repo root (moved under docs)
* docs: rename pm-agent-implementation-status.md -> PM_AGENT.md for clarity
* docs: update links to PM_AGENT.md after rename
---------
Co-authored-by: kazuki <kazuki@kazukinoMacBook-Air.local>
|
2025-10-15 21:07:39 +05:30 |
|
kazuki nakai
|
d27c53fa1c
|
Redesign PM Agent as Self-Improvement Meta-Layer (#421)
* feat: Add PM Agent (Project Manager Agent) for seamless orchestration
Introduces PM Agent as the default orchestration layer that coordinates
all sub-agents and manages workflows automatically.
Key Features:
- Default orchestration: All user interactions handled by PM Agent
- Auto-delegation: Intelligent sub-agent selection based on task analysis
- Docker Gateway integration: Zero-token baseline with dynamic MCP loading
- Self-improvement loop: Automatic documentation of patterns and mistakes
- Optional override: Users can specify sub-agents explicitly if desired
Architecture:
- Agent spec: SuperClaude/Agents/pm-agent.md
- Command: SuperClaude/Commands/pm.md
- Updated docs: README.md (15→16 agents), agents.md (new Orchestration category)
User Experience:
- Default: PM Agent handles everything (seamless, no manual routing)
- Optional: Explicit --agent flag for direct sub-agent access
- Both modes available simultaneously (no user downside)
Implementation Status:
- ✅ Specification complete
- ✅ Documentation complete
- ⏳ Prototype implementation needed
- ⏳ Docker Gateway integration needed
- ⏳ Testing and validation needed
Refs: kazukinakai/docker-mcp-gateway (IRIS MCP Gateway integration)
* feat: Add Agent Orchestration rules for PM Agent default activation
Implements PM Agent as the default orchestration layer in RULES.md.
Key Changes:
- New 'Agent Orchestration' section (CRITICAL priority)
- PM Agent receives ALL user requests by default
- Manual override with @agent-[name] bypasses PM Agent
- Agent Selection Priority clearly defined:
1. Manual override → Direct routing
2. Default → PM Agent → Auto-delegation
3. Delegation based on keywords, file types, complexity, context
User Experience:
- Default: PM Agent handles everything (seamless)
- Override: @agent-[name] for direct specialist access
- Transparent: PM Agent reports delegation decisions
This establishes PM Agent as the orchestration layer while
respecting existing auto-activation patterns and manual overrides.
Next Steps:
- Local testing in agiletec project
- Iteration based on actual behavior
- Documentation updates as needed
* refactor(pm-agent): redesign as self-improvement meta-layer
Problem Resolution:
PM Agent's initial design competed with existing auto-activation for task routing,
creating confusion about orchestration responsibilities and adding unnecessary complexity.
Design Change:
Redefined PM Agent as a meta-layer agent that operates AFTER specialist agents
complete tasks, focusing on:
- Post-implementation documentation and pattern recording
- Immediate mistake analysis with prevention checklists
- Monthly documentation maintenance and noise reduction
- Pattern extraction and knowledge synthesis
Two-Layer Orchestration System:
1. Task Execution Layer: Existing auto-activation handles task routing (unchanged)
2. Self-Improvement Layer: PM Agent meta-layer handles documentation (new)
Files Modified:
- SuperClaude/Agents/pm-agent.md: Complete rewrite with meta-layer design
- Category: orchestration → meta
- Triggers: All user interactions → Post-implementation, mistakes, monthly
- Behavioral Mindset: Continuous learning system
- Self-Improvement Workflow: BEFORE/DURING/AFTER/MISTAKE RECOVERY/MAINTENANCE
- SuperClaude/Core/RULES.md: Agent Orchestration section updated
- Split into Task Execution Layer + Self-Improvement Layer
- Added orchestration flow diagram
- Clarified PM Agent activates AFTER task completion
- README.md: Updated PM Agent description
- "orchestrates all interactions" → "ensures continuous learning"
- Docs/User-Guide/agents.md: PM Agent section rewritten
- Section: Orchestration Agent → Meta-Layer Agent
- Expertise: Project orchestration → Self-improvement workflow executor
- Examples: Task coordination → Post-implementation documentation
- PR_DOCUMENTATION.md: Comprehensive PR documentation added
- Summary, motivation, changes, testing, breaking changes
- Two-layer orchestration system diagram
- Verification checklist
Integration Validated:
Tested with agiletec project's self-improvement-workflow.md:
✅ PM Agent aligns with existing BEFORE/DURING/AFTER/MISTAKE RECOVERY phases
✅ Complements (not competes with) existing workflow
✅ agiletec workflow defines WHAT, PM Agent defines WHO executes it
Breaking Changes: None
- Existing auto-activation continues unchanged
- Specialist agents unaffected
- User workflows remain the same
- New capability: Automatic documentation and knowledge maintenance
Value Proposition:
Transforms SuperClaude into a continuously learning system that accumulates
knowledge, prevents recurring mistakes, and maintains fresh documentation
without manual intervention.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
---------
Co-authored-by: kazuki <kazuki@kazukinoMacBook-Air.local>
Co-authored-by: Claude <noreply@anthropic.com>
|
2025-10-12 14:22:10 +05:30 |
|