coulomb/markitect-main
2
0
Fork 0
Code Issues 61 Pull Requests Actions Projects 12 Releases 1 Wiki Activity

feat: reorganize capabilities directory structure for better separation

Browse Source 
- Move issue-facade submodule from root to capabilities/ directory
- Update .gitmodules to reflect new submodule path: capabilities/issue-facade
- Update all documentation references to new capability paths
- Update agent definitions with new issue-facade location
- Establish logical organization: capabilities/ for all external dependencies
- Maintain wiki/ at root as project documentation, not reusable capability

Improves separation between:
- Project infrastructure (wiki/ at root)
- Reusable capabilities (capabilities/ directory)
- Internal code (markitect/ directory)

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

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Bernd Worsch
2025-10-25 02:22:14 +02:00
parent 747715af58
commit 6233d13f18
7 changed files with 19 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
.gitmodules vendored
View File

@@ -2,6 +2,6 @@
path = wiki path = wiki
url = http://92.205.130.254:32166/coulomb/markitect_project.wiki.git url = http://92.205.130.254:32166/coulomb/markitect_project.wiki.git
branch = main branch = main
[submodule "issue-facade"] [submodule "capabilities/issue-facade"]
path = issue-facade path = capabilities/issue-facade
url = http://92.205.130.254:32166/coulomb/issue-facade.git url = http://92.205.130.254:32166/coulomb/issue-facade.git

8
CAPABILITY_INCLUSION_GUIDE.md
View File

@@ -75,7 +75,7 @@ markitect/cli/ # CLI framework capability
#### 1. **Submodule Capabilities** (Independent Repositories) #### 1. **Submodule Capabilities** (Independent Repositories)
- **Pattern**: Git submodules pointing to external repositories - **Pattern**: Git submodules pointing to external repositories
- **Benefits**: Independent versioning, separate development, easy updates - **Benefits**: Independent versioning, separate development, easy updates
- **Examples**: `issue-facade/`, `wiki/` - **Examples**: `capabilities/issue-facade/`, `wiki/`
#### 2. **Local Extracted Capabilities** (Previously Internal, Now Separated) #### 2. **Local Extracted Capabilities** (Previously Internal, Now Separated)
- **Pattern**: Moved to `capabilities/` directory but still in this repo - **Pattern**: Moved to `capabilities/` directory but still in this repo
@@ -125,7 +125,7 @@ Extract capability → Choose inclusion pattern → Update registries
Internal → markitect/issues/ (internal issue management) Internal → markitect/issues/ (internal issue management)
Evaluation → Self-contained, reusable, independent development needed Evaluation → Self-contained, reusable, independent development needed
Extraction → coulomb/issue-facade (separate repository) Extraction → coulomb/issue-facade (separate repository)
Inclusion → issue-facade/ (submodule capability) Inclusion → capabilities/issue-facade/ (submodule capability)
Registration → CAPABILITY_REGISTRY.md updated Registration → CAPABILITY_REGISTRY.md updated
``` ```
@@ -146,11 +146,11 @@ markitect/ # Core repository
### External Capabilities (4 documented in CAPABILITY_REGISTRY.md) ### External Capabilities (4 documented in CAPABILITY_REGISTRY.md)
``` ```
issue-facade/ # Submodule: Universal issue tracking
wiki/ # Submodule: Documentation
capabilities/ capabilities/
├── issue-facade/ # Submodule: Universal issue tracking
├── markitect-content/ # Local: Content processing ├── markitect-content/ # Local: Content processing
└── markitect-utils/ # Local: Utility functions └── markitect-utils/ # Local: Utility functions
wiki/ # Submodule: Documentation
[External dependencies: click, pytest, sqlalchemy, ...] [External dependencies: click, pytest, sqlalchemy, ...]
``` ```

8
CAPABILITY_REGISTRY.md
View File

@@ -25,11 +25,11 @@ Third-party packages providing specific capabilities via pip/pypi.
### Universal Issue Management ### Universal Issue Management
- **Type**: Submodule Capability - **Type**: Submodule Capability
- **Location**: `issue-facade/` - **Location**: `capabilities/issue-facade/`
- **Repository**: `coulomb/issue-facade` - **Repository**: `coulomb/issue-facade`
- **Purpose**: Backend-agnostic issue tracking with unified CLI - **Purpose**: Backend-agnostic issue tracking with unified CLI
- **Interfaces**: - **Interfaces**:
- CLI: `cd issue-facade && python -m cli.main [command]` - CLI: `cd capabilities/issue-facade && python -m cli.main [command]`
- API: Core models, backends (local SQLite, Gitea, GitHub, GitLab) - API: Core models, backends (local SQLite, Gitea, GitHub, GitLab)
- **Usage Guidelines**: - **Usage Guidelines**:
- ✅ **USE**: For all issue management tasks - ✅ **USE**: For all issue management tasks
@@ -95,7 +95,7 @@ Third-party packages providing specific capabilities via pip/pypi.
### Submodule Integration ### Submodule Integration
```bash ```bash
# Issue management # Issue management
cd issue-facade && python -m cli.main list cd capabilities/issue-facade && python -m cli.main list
# Documentation updates # Documentation updates
cd wiki && git pull origin main cd wiki && git pull origin main
@@ -137,7 +137,7 @@ import pytest # Testing framework
- **Utilities**: Check `markitect-utils` before creating new utility functions - **Utilities**: Check `markitect-utils` before creating new utility functions
### Integration Commands: ### Integration Commands:
- **Issue Operations**: `cd issue-facade && python -m cli.main [command]` - **Issue Operations**: `cd capabilities/issue-facade && python -m cli.main [command]`
- **Content Analysis**: Import from `capabilities.markitect_content` - **Content Analysis**: Import from `capabilities.markitect_content`
- **Utility Functions**: Import from `capabilities.markitect_utils` - **Utility Functions**: Import from `capabilities.markitect_utils`
- **Documentation**: Reference files in `wiki/` - **Documentation**: Reference files in `wiki/`

2
agents/agent-project-management.md
View File

@@ -48,7 +48,7 @@ You are the MarkiTect project assistant, specialized in providing project status
- **Issue Workflow**: Create → Triage → Plan → Schedule → Implement → Close - **Issue Workflow**: Create → Triage → Plan → Schedule → Implement → Close
**TDD Workflow Management:** **TDD Workflow Management:**
- For issue management tasks, use the **issue-facade** system located in `issue-facade/` - For issue management tasks, use the **issue-facade** system located in `capabilities/issue-facade/`
- The issue-facade provides unified CLI for GitHub, GitLab, Gitea, and local SQLite backends - The issue-facade provides unified CLI for GitHub, GitLab, Gitea, and local SQLite backends
- This includes sidequest management, test planning, and comprehensive development workflow guidance - This includes sidequest management, test planning, and comprehensive development workflow guidance

4
agents/agent-requirements-engineering.md
View File

@@ -117,7 +117,7 @@ python tools/requirements_engineering_toolkit.py validate-mocks --test-file test
# Enhanced Makefile targets # Enhanced Makefile targets
issue-start: validate-requirements issue-start: validate-requirements
# Use issue-facade for issue management # Use issue-facade for issue management
cd issue-facade && python -m cli.main show $(NUM) cd capabilities/issue-facade && python -m cli.main show $(NUM)
validate-requirements: validate-requirements:
python tools/requirements_engineering_toolkit.py analyze python tools/requirements_engineering_toolkit.py analyze
@@ -456,7 +456,7 @@ validate-requirements:
issue-start: validate-requirements issue-start: validate-requirements
# Use issue-facade for issue management # Use issue-facade for issue management
cd issue-facade && python -m cli.main show $(NUM) cd capabilities/issue-facade && python -m cli.main show $(NUM)
``` ```
### Tool Dependencies ### Tool Dependencies

12
agents/agent-tdd-workflow.md
View File

@@ -99,10 +99,10 @@ The **TDD8 cycle** is an 8-step comprehensive development workflow that extends
You are the authoritative guide for the TDD8 workflow using the issue-facade system for issue management. You understand how each step builds upon the previous ones and how sidequests can emerge at any stage of any software development project. You are the authoritative guide for the TDD8 workflow using the issue-facade system for issue management. You understand how each step builds upon the previous ones and how sidequests can emerge at any stage of any software development project.
**Primary Issue Management Commands:** **Primary Issue Management Commands:**
- Issue management via issue-facade: `cd issue-facade && python -m cli.main list` - Issue management via issue-facade: `cd capabilities/issue-facade && python -m cli.main list`
- `cd issue-facade && python -m cli.main show ISSUE_NUM` - Show issue details - `cd capabilities/issue-facade && python -m cli.main show ISSUE_NUM` - Show issue details
- `cd issue-facade && python -m cli.main create "Title" "Description"` - Create new issue - `cd capabilities/issue-facade && python -m cli.main create "Title" "Description"` - Create new issue
- `cd issue-facade && python -m cli.main close ISSUE_NUM` - Close completed issue - `cd capabilities/issue-facade && python -m cli.main close ISSUE_NUM` - Close completed issue
**Capability Awareness:** **Capability Awareness:**
- **Before implementing**: Check `CAPABILITY_REGISTRY.md` for existing functionality - **Before implementing**: Check `CAPABILITY_REGISTRY.md` for existing functionality
@@ -116,7 +116,7 @@ You are the authoritative guide for the TDD8 workflow using the issue-facade sys
- Tea CLI: `tea issue show NUM` - Show detailed view of specific issue - Tea CLI: `tea issue show NUM` - Show detailed view of specific issue
### Workspace Management Understanding ### Workspace Management Understanding
You understand the project structure with issue-facade for issue management: You understand the project structure with capabilities/issue-facade for issue management:
``` ```
{workspace_dir}/ {workspace_dir}/
├── current_issue.json # Active issue metadata ├── current_issue.json # Active issue metadata
@@ -157,7 +157,7 @@ You understand the project structure with issue-facade for issue management:
### TDDAi Framework Components ### TDDAi Framework Components
**Core Infrastructure:** **Core Infrastructure:**
- `issue-facade/` - Universal issue management facade - `capabilities/issue-facade/` - Universal issue management facade
- `workspace.py` - Workspace management - `workspace.py` - Workspace management
- `issue_fetcher.py` - Issue API integration - `issue_fetcher.py` - Issue API integration
- `issue_writer.py` - Issue updates via PATCH - `issue_writer.py` - Issue updates via PATCH

0
issue-facade → capabilities/issue-facade
View File