@akm1923main/init-project 1.0.0

package/templates/02_Skills/workflows/documentation_workflow.md

@@ -0,0 +1,352 @@
+---
+# 📄 documentation_workflow.md (Enterprise 9.5+)
+
+```md
+# 📘 Documentation Workflow (Enterprise Documentation Enforcement Layer)
+---
+# 1️⃣ Phase Objective
+
+Transform:
+
+- PRD
+- Architecture
+- Folder Structure
+- Implementation Structure
+- Decisions Log
+
+Into:
+
+- Professional-grade system documentation
+- Beginner-friendly explanation
+- Component-wise documentation
+- Visual diagrams (Mermaid + ASCII)
+- Folder-level explanations
+- Failure + security explanations
+
+This workflow prevents:
+
+- Shallow documentation
+- Architecture-document mismatch
+- Missing component explanation
+- No diagrams
+- Copy-paste generic docs
+- Onboarding confusion
+
+---
+
+# 2️⃣ Authority & Scope Boundaries
+
+This workflow IS authorized to:
+
+- Explain architecture
+- Explain folder structure
+- Generate diagrams
+- Create component-level docs
+- Add clarity layers
+- Add beginner explanations
+
+This workflow is NOT authorized to:
+
+- Change architecture
+- Modify PRD
+- Invent new features
+- Alter code
+- Redefine component boundaries
+
+If inconsistencies found:
+→ Escalate to Architect.
+
+---
+
+# 3️⃣ Entry Preconditions (STRICT GATE)
+
+Before starting documentation:
+
+- [ ] PRD.md exists
+- [ ] ARCHITECTURE.md exists
+- [ ] Folder structure stable
+- [ ] No open architectural blockers
+- [ ] Execution phase complete OR architecture finalized
+- [ ] PROJECT_STATE.md updated to appropriate phase
+
+If not satisfied → STOP.
+
+---
+
+# 4️⃣ Required Inputs
+
+You MUST read:
+
+- PRD.md
+- ARCHITECTURE.md
+- 05_Project/ folder structure
+- state/DECISIONS.md
+- PROJECT_STATE.md
+- DEVELOPMENT_CHECKLIST.md (if execution done)
+
+Missing any → STOP.
+
+---
+
+# 5️⃣ Documentation Coverage Planning
+
+Before writing documentation:
+
+## Step 1 — Component Identification
+
+List:
+
+- All major architectural components
+- All layers
+- External integrations
+- Cross-cutting concerns
+
+Ensure no component left undocumented.
+
+---
+
+## Step 2 — Documentation Map Creation
+
+Plan structure:
+
+```
+
+06_Documentation/
+│
+├── SYSTEM_OVERVIEW.md
+├── ARCHITECTURE.md
+│
+├── COMPONENT_/
+│ ├── OVERVIEW.md
+│ ├── DATA_FLOW.md
+│ ├── FAILURE_MODEL.md
+│ ├── SECURITY_MODEL.md
+│ └── INTERNAL_STRUCTURE.md
+
+```
+
+Each component must be uniquely documented.
+No duplicate templates allowed.
+
+---
+
+# 6️⃣ Structured Documentation Execution
+
+---
+
+## Phase A — System Overview Documentation
+
+Must include:
+
+- Problem explanation (simple)
+- System role
+- High-level architecture
+- Technology stack
+- ASCII system diagram
+- Mermaid C4 diagram
+- Scaling explanation
+- Security boundary overview
+- Failure overview
+
+Beginner-friendly explanation required.
+
+---
+
+## Phase B — Architecture Documentation
+
+Must include:
+
+- Folder structure (ASCII)
+- Component responsibility mapping
+- Data flow diagrams
+- Sequence diagrams
+- Failure model summary
+- Security model summary
+- Observability explanation
+- Deployment topology overview
+
+Diagrams mandatory.
+
+---
+
+## Phase C — Component-Level Documentation
+
+For EACH component:
+
+Generate:
+
+### 1. OVERVIEW.md
+
+- Purpose
+- Responsibility
+- What it does NOT do
+- Interaction boundaries
+- Beginner explanation
+
+### 2. DATA_FLOW.md
+
+- Mermaid sequence diagram
+- ASCII flow diagram
+- Step-by-step explanation
+
+### 3. FAILURE_MODEL.md
+
+- Failure cases
+- Retry logic
+- Timeout logic
+- Error propagation
+- Circuit breaker (if exists)
+
+### 4. SECURITY_MODEL.md
+
+- Auth boundaries
+- Authorization
+- Input validation
+- Data sensitivity
+
+### 5. INTERNAL_STRUCTURE.md
+
+- Class/module structure
+- Dependency direction
+- Internal diagrams
+- Why structured that way
+
+No component documentation may be shallow.
+
+---
+
+# 7️⃣ Diagram Enforcement Rules
+
+Each of these must include diagrams:
+
+- System Overview → 1 Mermaid + 1 ASCII
+- Architecture → 2+ Mermaid + ASCII folder tree
+- Each Component → At least 1 Mermaid + 1 ASCII
+
+No placeholder diagrams allowed.
+
+Diagrams must reflect actual architecture.
+
+---
+
+# 8️⃣ Beginner Accessibility Layer
+
+Each major documentation file must include:
+
+Section titled:
+
+"🧒 If you're new"
+
+Explain:
+
+- Core concept simply
+- Real-world analogy
+- Plain English explanation
+
+Documentation must be understandable to:
+
+- New developer
+- Junior engineer
+- Technical intern
+
+Without losing accuracy.
+
+---
+
+# 9️⃣ Consistency Validation Gate
+
+Before completion:
+
+Validate:
+
+- Component names match architecture
+- Folder names match actual repo
+- Technology stack matches architecture
+- No outdated terminology
+- No drift from PRD
+- Diagrams reflect current system
+
+If drift detected:
+→ Escalate to Architect.
+
+---
+
+# 🔟 Quality Checklist (MANDATORY BEFORE PHASE CLOSE)
+
+- [ ] System overview complete
+- [ ] Architecture explanation complete
+- [ ] All components documented
+- [ ] Failure model explained
+- [ ] Security model explained
+- [ ] Folder structure documented
+- [ ] Mermaid diagrams included
+- [ ] ASCII diagrams included
+- [ ] Beginner explanation included
+- [ ] No copy-paste repetition
+- [ ] Terminology consistent
+
+If any unchecked → Phase incomplete.
+
+---
+
+# 1️⃣1️⃣ State Update Protocol
+
+After documentation generation:
+
+1. Update PROJECT_STATE.md:
+   - Documentation Phase → Completed
+2. Append entry in PROGRESS_LOG.md:
+   - Date
+   - Components documented
+3. If new drift discovered:
+   - Log issue
+   - Escalate
+
+---
+
+# 1️⃣2️⃣ Resume Logic
+
+If documentation phase interrupted:
+
+Resume by:
+
+- Checking which components documented
+- Verifying consistency
+- Continuing missing components
+- Re-validating diagrams
+
+Do NOT regenerate everything blindly.
+
+---
+
+# 1️⃣3️⃣ Anti-Patterns to Avoid
+
+- Copying architecture file verbatim
+- Generic explanations
+- No diagrams
+- Ignoring failure model
+- Ignoring security model
+- Repeating same template blindly
+- Writing marketing-style text
+- Overly technical without beginner layer
+
+---
+
+# 1️⃣4️⃣ Success Criteria
+
+Documentation is considered enterprise-grade when:
+
+- New developer can onboard without code reading
+- Architecture is visually understandable
+- Component responsibilities are clear
+- Failure paths explained
+- Security boundaries explicit
+- Diagrams accurate
+- Folder structure justified
+- No ambiguity remains
+
+Documentation reduces onboarding time.
+Documentation reduces architecture drift.
+Documentation increases system clarity.
+
+You are building clarity infrastructure.

package/templates/02_Skills/workflows/idea_refinement_workflow.md

@@ -0,0 +1,106 @@
+
+# 🧠 Idea Refinement Workflow (Concept Discipline Layer)
+
+---
+
+# Phase Objective
+
+Transform raw idea into structured, bounded, risk-aware conceptual document.
+
+---
+
+# Entry Preconditions
+
+- Raw idea provided
+- No active upstream contradictions
+- PROJECT_STATE allows idea phase
+
+---
+
+# Required Artifact
+
+03_Project_Info/Idea_Analyst/IDEA.md
+
+---
+
+# Structured Execution
+
+## Step 1: Input Clarity Scan
+
+- Identify vague terms
+- Identify missing actors
+- Identify missing constraints
+- Identify hidden assumptions
+
+If unclear → ask clarifying questions.
+
+---
+
+## Step 2: Problem Precision
+
+Define:
+
+- Who suffers?
+- What pain?
+- Why now?
+- What happens if not solved?
+
+---
+
+## Step 3: Assumption Extraction
+
+List:
+
+- Technical assumptions
+- User behavior assumptions
+- Resource assumptions
+
+---
+
+## Step 4: Scope Bounding
+
+Define:
+
+- In Scope
+- Out of Scope
+- MVP boundary
+
+---
+
+## Step 5: Risk Exposure
+
+Surface:
+
+- Feasibility risk
+- Adoption risk
+- Resource risk
+
+---
+
+# Exit Validation
+
+- [ ] Problem defined
+- [ ] Scope bounded
+- [ ] Risks listed
+- [ ] Assumptions documented
+- [ ] No architecture references
+
+---
+
+# Escalation Matrix
+
+| Issue                   | Escalate To      |
+| ----------------------- | ---------------- |
+| Business contradiction  | Business Analyst |
+| Technical impossibility | Flag explicitly  |
+
+---
+
+# State Update
+
+Update:
+
+- PROJECT_STATE.md
+- PROGRESS_LOG.md
+
+Recommend Business Analysis.

package/templates/02_Skills/workflows/performance_review_workflow.md

@@ -0,0 +1,29 @@
+
+# ⚡ Performance Review Workflow
+
+---
+
+# Entry Preconditions
+
+- Security review complete
+
+---
+
+# Structured Execution
+
+## Step 1: Target validation
+
+## Step 2: Bottleneck scan
+
+## Step 3: DB efficiency check
+
+## Step 4: Load simulation
+
+## Step 5: Risk classification
+
+---
+
+# Exit Validation
+
+- [ ] Bottlenecks identified
+- [ ] Optimization suggestions documented

package/templates/02_Skills/workflows/prd_generation_workflow.md

@@ -0,0 +1,83 @@
+# 📌 PRD Generation Workflow (Requirements Enforcement Layer)
+
+---
+
+# Phase Objective
+
+Produce measurable, testable, architecture-consumable PRD.
+
+---
+
+# Entry Preconditions
+
+- IDEA.md exists
+- Business viability assessed
+- No unresolved conceptual contradictions
+
+---
+
+# Required Artifact
+
+03_Project_Info/Product_Manager/PRD.md
+
+---
+
+# Structured Execution
+
+## Step 1: Scope Lock
+
+Define MVP explicitly before FR writing.
+
+## Step 2: Goal Formalization
+
+Convert all goals to measurable statements.
+
+## Step 3: Persona Structuring
+
+Detailed personas only.
+
+## Step 4: Use Case Modeling
+
+Include:
+
+- Failure flows
+- Alternate flows
+
+## Step 5: FR Authoring
+
+Rules:
+
+- Atomic
+- Measurable
+- Traceable to use case
+
+## Step 6: NFR Definition
+
+Must define:
+
+- Performance targets
+- Reliability targets
+- Security baseline
+- Scalability expectations
+
+---
+
+# Exit Validation
+
+- [ ] All FR atomic
+- [ ] NFR measurable
+- [ ] Non-goals listed
+- [ ] No tech stack references
+
+---
+
+# Escalation
+
+PRD contradiction → Idea_Analyst
+Unrealistic goal → Business_Analyst
+
+---
+
+# State Update
+
+Recommend Architect.

package/templates/02_Skills/workflows/refactor_workflow.md

@@ -0,0 +1,35 @@
+
+# 🔁 Refactor Workflow (Tech Debt Discipline)
+
+---
+
+# Phase Objective
+
+Improve structure without behavioral change.
+
+---
+
+# Entry Preconditions
+
+- Testing green
+- No active feature tasks
+
+---
+
+# Structured Execution
+
+## Step 1: Identify complexity hotspots
+
+## Step 2: Ensure no behavior change
+
+## Step 3: Maintain test coverage
+
+## Step 4: Improve modularity
+
+---
+
+# Exit Validation
+
+- [ ] No functionality changed
+- [ ] Tests still passing
+- [ ] Complexity reduced

package/templates/02_Skills/workflows/security_audit_workflow.md

@@ -0,0 +1,30 @@
+
+# 🔐 Security Audit Workflow (Threat Enforcement)
+
+---
+
+# Entry Preconditions
+
+- Architecture complete
+- Implementation complete
+
+---
+
+# Structured Execution
+
+## Step 1: Asset identification
+
+## Step 2: Threat modeling
+
+## Step 3: Code surface scan
+
+## Step 4: OWASP alignment
+
+## Step 5: Risk classification
+
+---
+
+# Exit Validation
+
+- [ ] Threat model defined
+- [ ] Vulnerabilities classified

package/templates/02_Skills/workflows/task_execution_workflow.md

@@ -0,0 +1,33 @@
+
+# ⚙ Task Execution Workflow (Implementation Discipline)
+
+---
+
+# Entry Preconditions
+
+- TASK_PLAN exists
+- Dependencies satisfied
+
+---
+
+# Structured Execution
+
+## Step 1: Review task file
+
+## Step 2: Validate dependencies
+
+## Step 3: Implement strictly within scope
+
+## Step 4: Validate acceptance criteria
+
+## Step 5: Update checklist
+
+## Step 6: Update state
+
+---
+
+# Anti-Patterns
+
+- Multi-task implementation
+- Architecture modification
+- Checklist skipping

package/templates/02_Skills/workflows/task_generation_workflow.md

@@ -0,0 +1,61 @@
+
+# 🧩 Task Generation Workflow (Execution Blueprint Layer)
+
+---
+
+# Phase Objective
+
+Convert architecture into atomic, dependency-aware tasks.
+
+---
+
+# Entry Preconditions
+
+- ARCHITECTURE.md complete
+
+---
+
+# Required Artifacts
+
+04_Tasks/TASK_PLAN.md
+04_Tasks/DEVELOPMENT_CHECKLIST.md
+04_Tasks/TASKS/*.md
+
+---
+
+# Structured Execution
+
+## Step 1: Architecture Decomposition
+
+Break into layers.
+
+## Step 2: Task Atomization
+
+Each task must:
+
+- Single responsibility
+- Acceptance criteria
+- Hard/Soft dependencies
+- Complexity tag
+
+## Step 3: Dependency Graph
+
+Generate Mermaid graph.
+
+## Step 4: Critical Path Marking
+
+Mark 🔴 tasks.
+
+---
+
+# Exit Validation
+
+- [ ] All components mapped
+- [ ] No circular dependencies
+- [ ] All tasks atomic
+
+---
+
+# State Update
+
+Recommend Task Execution.