@akm1923main/init-project 1.0.0 → 1.2.0

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

@@ -1,70 +1,114 @@
-
 # 📊 Business Analysis Workflow (Commercial Viability Layer)
 
 ---
 
+# Workflow Metadata
+
+| Field | Value |
+|-------|-------|
+| **Workflow ID** | WF-02 |
+| **Phase** | 02 — Business Analysis |
+| **Bound Agent** | Business_Analyst |
+| **Output Artifact** | `03_Project_Info/Business_Analyst/PRODUCT_ANALYSIS.md` |
+| **Version** | 2.0 |
+
+---
+
 # Phase Objective
 
-Evaluate commercial feasibility and market positioning.
+Evaluate commercial feasibility and market positioning of the refined idea.
 
 ---
 
-# Entry Preconditions
+# 1️⃣ INITIALIZE
 
-- IDEA.md exists
-- Idea phase marked complete
+1. Read `PROJECT_STATE.md` — confirm Phase 01 complete, Phase 02 current
+2. Read `03_Project_Info/Idea_Analyst/IDEA.md`
+3. If resuming, read last `PROGRESS_LOG.md` entry
 
 ---
 
-# Required Artifact
+# 2️⃣ VALIDATE (Entry Gate)
+
+- [ ] `IDEA.md` exists and is complete
+- [ ] Phase 01 marked complete in `PROJECT_STATE.md`
+- [ ] No unresolved escalations from Phase 01
 
-03_Project_Info/Business_Analyst/PRODUCT_ANALYSIS.md
+If any check fails → HALT and report.
 
 ---
 
-# Structured Execution
+# 3️⃣ EXECUTE (Structured Steps)
 
 ## Step 1: Market Research
+- Market size, trends, growth signals, geographic context
 
-- Market size
-- Trends
-- Growth signals
+**Acceptance Criteria:** Market context defined with supporting evidence.
 
 ## Step 2: Competitor Mapping
+- Direct competitors, indirect substitutes, differentiation gaps
 
-- Direct competitors
-- Indirect substitutes
-- Differentiation gaps
+**Acceptance Criteria:** At least 3 competitors identified and compared.
 
 ## Step 3: Monetization Modeling
+- Who pays? Why? Revenue model options evaluated
 
-- Who pays?
-- Why?
-- Revenue model options
+**Acceptance Criteria:** At least 2 monetization strategies evaluated.
 
 ## Step 4: SWOT Analysis
+- Strengths, Weaknesses, Opportunities, Threats
 
-- Strengths
-- Weaknesses
-- Opportunities
-- Threats
+**Acceptance Criteria:** All four quadrants populated with substance.
 
 ## Step 5: Risk Classification
+- Classify viability: Strong / Moderate / High Risk / Weak
 
-Strong / Moderate / High Risk / Weak
+**Acceptance Criteria:** Classification justified with evidence.
 
 ---
 
-# Exit Validation
+# 4️⃣ VERIFY (Exit Gate)
 
 - [ ] Market defined
 - [ ] Competition listed
 - [ ] Monetization evaluated
+- [ ] SWOT completed
 - [ ] Risks classified
 - [ ] Viability conclusion justified
+- [ ] No technical architecture discussed
+
+If any check fails → revisit corresponding step.
+
+---
+
+# 5️⃣ CLOSE
+
+1. Finalize `03_Project_Info/Business_Analyst/PRODUCT_ANALYSIS.md`
+2. Recommend: `Product_Manager` (if viable) or suggest pivot (if weak)
+
+---
+
+# 6️⃣ STATE SYNC
+
+1. Update `PROJECT_STATE.md`:
+   - Phase 02: Completed
+   - Viability: <classification>
+   - Next: Product_Manager (Phase 03)
+
+2. Append to `04_Tasks/PROGRESS_LOG.md`:
+```
+## <date>
+Phase 02: Business Analysis — Completed.
+Agent: Business_Analyst
+Viability: <Strong/Moderate/High Risk/Weak>
+Next: Product_Manager (Phase 03)
+```
 
 ---
 
-# State Update
+# Resume Logic
 
-Update state and recommend PRD generation.
+If interrupted:
+- Check if PRODUCT_ANALYSIS.md partially exists
+- Resume from last incomplete step
+- Do NOT restart research from scratch

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

@@ -1,31 +1,116 @@
+# 🚀 Deployment Workflow (Platform-Specific Execution Layer)
 
-# 🚀 Deployment Workflow (Platform-Specific)
+---
+
+# Workflow Metadata
+
+| Field | Value |
+|-------|-------|
+| **Workflow ID** | WF-11 |
+| **Phase** | 11 — Deployment |
+| **Bound Agent** | Deployment_Engineer |
+| **Output Artifact** | `03_Project_Info/Deployment_Engineer/DEPLOYMENT_GUIDE_<PLATFORM>.md` |
+| **Version** | 2.0 |
 
 ---
 
-# Entry Preconditions
+# Phase Objective
 
-- DevOps plan complete
-- Platform specified
+Transform DevOps strategy into platform-specific, step-by-step deployment instructions.
 
 ---
 
-# Structured Execution
+# 1️⃣ INITIALIZE
 
-## Step 1: Compatibility validation
+1. Read `PROJECT_STATE.md` — confirm Phase 10 complete
+2. Read Architecture, DevOps Plan, Security Audit, Performance Report
+3. Determine target platform (ask user if not specified)
+4. If resuming, read last `PROGRESS_LOG.md` entry
 
-## Step 2: Web research
+---
 
-## Step 3: Step-by-step guide construction
+# 2️⃣ VALIDATE (Entry Gate)
 
-## Step 4: Troubleshooting section
+- [ ] DevOps plan complete (Phase 10)
+- [ ] Platform specified by user
+- [ ] Architecture available
+- [ ] No critical unresolved issues
 
-## Step 5: Rollback definition
+If any check fails → HALT.
 
 ---
 
-# Exit Validation
+# 3️⃣ EXECUTE (Structured Steps)
+
+## Step 1: Compatibility Validation
+- Validate platform supports required runtime, DB, workers, WebSockets
+
+**Acceptance Criteria:** Compatibility assessment documented.
+
+## Step 2: Web Research
+- Research platform-specific documentation, best practices, constraints
+
+**Acceptance Criteria:** Platform documentation referenced with current information.
+
+## Step 3: Step-by-Step Guide Construction
+- Create detailed deployment steps with exact commands, UI paths, validation methods
+
+**Acceptance Criteria:** Each step includes command, expected output, common mistakes.
+
+## Step 4: Troubleshooting Section
+- Document common issues and resolution steps
+
+**Acceptance Criteria:** At least 5 common issues documented with solutions.
+
+## Step 5: Rollback Definition
+- Platform-specific revert procedure
+
+**Acceptance Criteria:** Rollback procedure documented with exact steps.
+
+## Step 6: Cost & Production Notes
+- Free tier limits, cost warnings, production hardening
+
+**Acceptance Criteria:** Cost awareness documented, production checklist complete.
 
-- [ ] Deployment steps complete
+---
+
+# 4️⃣ VERIFY (Exit Gate)
+
+- [ ] Deployment steps complete and specific
 - [ ] Troubleshooting included
 - [ ] Rollback included
+- [ ] Cost notes included
+- [ ] Production checklist included
+- [ ] Readiness classified
+- [ ] No code modified
+
+---
+
+# 5️⃣ CLOSE
+
+1. Finalize deployment guide
+2. Mark pipeline COMPLETE
+3. Optionally recommend: `Refactor_Specialist` or `Documentation_Writer`
+
+---
+
+# 6️⃣ STATE SYNC
+
+1. Update `PROJECT_STATE.md`
+2. Append to `04_Tasks/PROGRESS_LOG.md`:
+```
+## <date>
+Phase 11: Deployment — Completed.
+Agent: Deployment_Engineer
+Platform: <platform>
+Readiness: <classification>
+Pipeline Status: COMPLETE
+```
+
+---
+
+# Resume Logic
+
+If interrupted:
+- Check which guide sections exist
+- Resume from first incomplete section

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

@@ -1,30 +1,117 @@
+# 🚀 DevOps Setup Workflow (Operational Automation Layer)
 
-# 🚀 DevOps Setup Workflow
+---
+
+# Workflow Metadata
+
+| Field | Value |
+|-------|-------|
+| **Workflow ID** | WF-10 |
+| **Phase** | 10 — DevOps Planning |
+| **Bound Agent** | DevOps_Engineer |
+| **Output Artifact** | `03_Project_Info/DevOps_Engineer/DEVOPS_PLAN.md` |
+| **Version** | 2.0 |
 
 ---
 
-# Entry Preconditions
+# Phase Objective
 
-- Performance reviewed
+Define CI/CD, containerization, infrastructure, and operational automation strategy.
 
 ---
 
-# Structured Execution
+# 1️⃣ INITIALIZE
 
-## Step 1: Environment modeling
+1. Read `PROJECT_STATE.md` — confirm Phase 09 complete
+2. Read Architecture, Performance Report, Security Audit
+3. If resuming, read last `PROGRESS_LOG.md` entry
 
-## Step 2: CI/CD pipeline modeling
+---
 
-## Step 3: Containerization strategy
+# 2️⃣ VALIDATE (Entry Gate)
 
-## Step 4: Rollback strategy
+- [ ] Performance reviewed (Phase 09)
+- [ ] Architecture available
+- [ ] Security audit available
+- [ ] No critical unresolved issues
 
-## Step 5: Production checklist
+If any check fails → HALT.
 
 ---
 
-# Exit Validation
+# 3️⃣ EXECUTE (Structured Steps)
+
+## Step 1: Environment Modeling
+- Define Local, Dev, Staging, Production environments
+- Define config isolation and data separation
+
+**Acceptance Criteria:** All environments defined with isolation strategy.
+
+## Step 2: CI/CD Pipeline Modeling
+- Define pipeline stages from checkout to production deploy
+- Define trigger conditions, branch strategy, failure behavior
+
+**Acceptance Criteria:** Pipeline fully defined with all stages.
+
+## Step 3: Containerization Strategy
+- Define Docker usage, multi-stage builds, image optimization
+
+**Acceptance Criteria:** Containerization approach documented (or justification for not using).
+
+## Step 4: Rollback Strategy
+- Define blue-green or rolling deployment
+- Define rollback triggers and procedure
+
+**Acceptance Criteria:** Rollback mechanism clearly defined.
+
+## Step 5: Secrets & Config Strategy
+- Define env var handling, secret storage, rotation
+
+**Acceptance Criteria:** No hardcoded secrets path documented.
+
+## Step 6: Production Checklist
+- Complete production readiness checklist
+
+**Acceptance Criteria:** All checklist items addressed.
+
+---
+
+# 4️⃣ VERIFY (Exit Gate)
 
 - [ ] CI/CD defined
+- [ ] Environments defined
 - [ ] Rollback defined
 - [ ] Secrets externalized
+- [ ] Monitoring defined
+- [ ] Production checklist complete
+- [ ] No code modified
+
+---
+
+# 5️⃣ CLOSE
+
+1. Finalize `03_Project_Info/DevOps_Engineer/DEVOPS_PLAN.md`
+2. Recommend: `Deployment_Engineer`
+
+---
+
+# 6️⃣ STATE SYNC
+
+1. Update `PROJECT_STATE.md`
+2. Append to `04_Tasks/PROGRESS_LOG.md`:
+```
+## <date>
+Phase 10: DevOps Planning — Completed.
+Agent: DevOps_Engineer
+CI/CD: Defined
+Maturity: <classification>
+Next: Deployment_Engineer (Phase 11)
+```
+
+---
+
+# Resume Logic
+
+If interrupted:
+- Check which DevOps plan sections exist
+- Resume from first incomplete section