メニュー
Use when generating or repairing layered AGENTS.md project guidance from verified repository structure, technology, data, and planning conventions.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/peterbamuhigire/chwezi-dev-engine --skill doc-architectコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
SKILL.md を表示中
| name | doc-architect |
| description | Use when generating or repairing layered AGENTS.md project guidance from verified repository structure, technology, data, and planning conventions. |
| metadata | {"portable":true,"compatible_with":["claude-code","codex"]} |
Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.
| Category | Artifact | Format | Example |
|---|---|---|---|
| Release evidence | Triple-Layer AGENTS.md output | Generated AGENTS.md covering project tech stack, data directory, and planning directory layers | AGENTS.md |
references/ directory for deep detail after reading the core workflow below.templates/ directory when the task needs a structured deliverable.protocols/ directory for formal execution order or handoff rules.Design and generate a portable Triple-Layer AGENTS.md documentation set that reflects the project’s real structure and constraints.
Modularize Instructions (Token Economy): Avoid consolidating all AI/dev guidance into a single AGENTS.md. Prefer smaller, focused docs (e.g., docs/setup.md, docs/api.md, docs/workflows.md) and reference them only when needed.
Documentation Standards (MANDATORY): ALL generated markdown files must follow strict formatting rules:
doc-standards.md for complete requirementsProduce three aligned AGENTS.md files:
The skill should activate when the user asks to:
Scan the workspace
Identify the environment
Set up plan grouping (first-time)
docs/plans/<module>/ subdirectories for each discovered module/area.docs/plans/AGENTS.md with the current module list.docs/plans/INDEX.md as the master plan status index.docs/plans/AGENTS.md updated whenever plans are added or their status changes.docs/plans/AGENTS.md and update it when requested.Generate Triple-Layer docs
If a project uses Laravel + MySQL with docs/plans and database/schema:
When generating AGENTS.md files, be aware of the complete SDLC documentation ecosystem:
| Skill | Phase | Documents Generated | When to Reference |
|---|---|---|---|
sdlc-planning | Planning | Vision, SDP, SRS, SCMP, QA Plan, Risk Plan, Feasibility | When plans directory contains SDLC planning docs |
sdlc-design | Design | SDD, Tech Spec, ICD, Database Design, API Docs, Code Standards | When referencing architecture and design decisions |
sdlc-testing | Testing | Test Plan, Test Cases, V&V Plan, Test Report, Peer Reviews | When referencing testing and quality standards |
sdlc-user-deploy | Delivery | User Manual, Ops Guide, Training, Release Notes, Maintenance, README | When referencing deployment and user documentation |
| Skill | Purpose | Relationship |
|---|---|---|
project-requirements | Raw requirements interview | Input source for SDLC planning docs |
feature-planning | Feature-level specs + implementation plans | Stored in docs/plans/ (planning directory) |
manual-guide | End-user manuals and guides | Stored in /manuals/ (separate from AGENTS.md) |
update-Codex-documentation | Keep project docs (README, AGENTS.md) updated | Maintains project-level docs after changes |
When scanning for documentation, expect this structure in projects using SDLC skills:
docs/
├── planning/ # sdlc-planning output (7 docs)
├── design/ # sdlc-design output (6 docs)
├── testing/ # sdlc-testing output (5 docs)
├── user-deploy/ # sdlc-user-deploy output (6 docs)
├── plans/ # feature-planning output
│ ├── AGENTS.md # Plans directory index (doc-architect manages this)
│ ├── INDEX.md # Plan status tracker
│ └── specs/ # Feature specifications
└── project-requirements/ # project-requirements output
Integration Rule: When generating the Planning AGENTS.md (docs/plans/AGENTS.md), include references to any SDLC documentation directories that exist alongside the plans directory.
| Condition | Action |
|---|---|
| Existing guidance is accurate | Preserve and extend it |
| Repository fact is uncertain | Inspect source files first |
| Rule belongs to one subtree | Put it in the nearest scoped file |
Read and search are required. Editing requires authorisation.
Fallback: without repository access, return a template and confirmation questions instead of inventing details.
| Artefact | Required? | Purpose |
|---|---|---|
| Audience, decisions, source material, document set, and maintenance owner | yes | Design information architecture |