# Project Management & Workflow Templates (v3.0 - Data-Centric & AI-Driven) This directory contains standardized process templates designed to guide AI-assisted project execution. This system emphasizes a **data-centric approach**, where the AI maintains a comprehensive `project_state` (defined in `[[support/DEFINE-ProjectStateSchema.md]]`). The AI takes a proactive role in proposing content, plans, and analyses, which the user then reviews and validates primarily through **structured yes/no questions**. Human-readable outputs are typically generated as specific deliverables from the project state, rather than being the default output of every process step. **Core Workflow (Located in `templates/project/`):** These templates represent the main phases of a project lifecycle, aligned with PMBOK principles. They should generally be used sequentially. The AI will prompt for the next template file when a phase is completed or a new process is required. 1. **[[archive/templates/projects/00-EXPLORE-ProjectIdea]]**: * **Purpose:** AI-facilitated brainstorming and idea refinement. * **AI Action:** Interprets user's freeform input, explores knowledge, proposes connections/expansions, and validates understanding via yes/no questions. * **Output:** Populates `project_state.exploration_history`. Outputs YAML summary upon user confirmation to proceed. Prompts for `01-INITIATE-Project.md`. 2. **[[archive/templates/projects/01-INITIATE-Project]]**: * **Purpose:** Formal project definition. * **AI Action:** Autonomously drafts a Project Charter based on exploration/user input. Presents for user review and approval/refinement via yes/no questions. Optionally initiates creation of supporting documents (Glossary, Style Guide, etc.) by proposing their initial content. * **Output:** Formalized `project_state.charter` (also as YAML). Prompts for `02-PLAN-ProjectExecution.md`. 3. **[[archive/templates/projects/02-PLAN-ProjectExecution]]**: * **Purpose:** Detailed project planning. * **AI Action:** Autonomously drafts a Project Plan (WBS, resources, risks, quality) based on the Charter. Performs internal critique. Presents refined plan for user approval/refinement via yes/no questions. * **Output:** Formalized `project_state.plan` (also as YAML). Prompts for `03-EXECUTE-Task.md`. 4. **[[archive/templates/projects/03-EXECUTE-Task]]**: * **Purpose:** Execution of individual project tasks. * **AI Action:** Confirms task understanding, proposes approach, executes work (directly or by dispatching to specialized templates in `special/`), self-critiques output, presents output/summary for user acceptance via yes/no questions. * **Output:** Updates `project_state.execution.tasks` (with output data, provenance). Proposes next logical step and prompts for the relevant template file (e.g., another `03-EXECUTE-Task.md`, `support/REVIEW-Feedback.md`, or `04-MONITOR_CONTROL-Performance.md`). 5. **[[archive/templates/projects/04-MONITOR_CONTROL-Performance]]**: * **Purpose:** Periodic or event-driven project review. * **AI Action:** Analyzes `project_state` for progress, variances, risks, and issues. Proposes assessments and strategic interventions. Facilitates user decisions via yes/no questions. * **Output:** Updates `project_state.monitoring_control` and other relevant state sections. Proposes next logical step and prompts for the relevant template file. 6. **[[05-Close]]**: * **Purpose:** Formal project or phase closure. * **AI Action:** Proposes a final report (outcomes, lessons learned, archival plan) based on `project_state`. User confirms/refines. * **Output:** Formalized `project_state.closure` (also as YAML). Prompts for follow-on work templates if applicable. --- **Supporting Templates (`templates/project/support/`)** These templates guide processes for creating and managing specific project artifacts, conducting common analyses, or facilitating project operations. They are typically invoked by the AI as part of a core workflow step (e.g., during `01-INITIATE-Project.md` or `03-EXECUTE-Task.md`) or by direct user request if needed. They all operate on and update the `project_state` data. * **Schema Definition:** * `[[support/DEFINE-ProjectStateSchema.md]]`: **(MASTER REFERENCE)** The blueprint for the entire `project_state` data object. Not executed, but referenced by all other templates. * **Project Setup & Governance Definitions:** * `[[support/DEFINE-CollaborationGuidelines.md]]`: Process to establish user-AI interaction rules. * `[[support/DEFINE-Glossary.md]]`: Process to create and maintain a project glossary. * `[[support/DEFINE-StyleGuide.md]]`: Process to create a project-specific style guide. * `[[support/DEFINE-SuccessMetrics.md]]`: Process to define KPIs and acceptance criteria. * **Logging & Tracking:** * `[[support/LOG-Decisions.md]]`: Process for recording key project decisions. * `[[support/LOG-Insights.md]]`: Process for capturing ad-hoc insights. * **Review & Analysis:** * `[[support/REVIEW-Feedback.md]]`: Process for capturing user feedback on deliverables. * `[[support/REVIEW-ProcessEffectiveness.md]]`: Process for evaluating and improving the project workflow itself. * `[[support/ANALYZE-Critique.md]]`: Process for critical evaluation of artifacts. * `[[support/ANALYZE-Data.md]]`: Process for documenting data analysis. * `[[support/ANALYZE-LiteratureReview.md]]`: Process for conducting and documenting literature reviews. * `[[support/ANALYZE-Logic-CriticalAnalysis.md]]`: Process for checking logical soundness. * **Specialized Planning:** * `[[support/PLAN-Research_Extension.md]]`: Process for planning follow-on work or project sequels. --- **Specialized Templates (`templates/project/special/`)** These templates represent more complex, specific methodologies, content generation tasks, or analytical tools. They are typically invoked by the AI as part of an `03-EXECUTE-Task.md` process when the Project Plan calls for such a specialized activity. They operate on and update the `project_state` data. * **CAFE Framework Components (for Foundational Exploratory Research):** * `[[special/PROCESS-Adaptive_Framework_Exploration.md]]`: The overarching CAFE methodology guide (reference). * `[[special/DEFINE-Framework_State.md]]`: Defines the structure for the `framework_states` data object. * `[[special/DEFINE-Parameter_Ledger.md]]`: Defines the structure for the `parameter_ledgers` data object. * `[[special/PROCESS-Synthesis_Cycle.md]]`: Process for a CAFE synthesis cycle. * `[[special/PROCESS-Strategy_Review_Cycle.md]]`: Process for a CAFE strategy review cycle. * `[[special/PROCESS-VS_Assessment_Cycle.md]]`: Process for a CAFE validation stage assessment. * `[[special/ANALYZE-Formalism_Candidate.md]]`: Process for assessing formalism candidates. * **Content Generation:** * `[[special/GENERATE-AcademicManuscriptMultiChapter.md]]`: Process for generating multi-chapter academic works. * `[[special/GENERATE-ManuscriptCompletionRevision.md]]`: Process for completing/revising manuscript drafts. * `[[special/GENERATE-SummaryTargeted.md]]`: Process for creating targeted summaries. * `[[special/GENERATE-USPTOPatentMinimalist.md]]`: Process for generating USPTO patent applications. * **Advanced Analysis & Extraction:** * `[[special/PROCESS-ConceptualGraph-TextAnalysis.md]]`: Process for conceptual graph analysis. * `[[special/PROCESS-Consilience_Framework-Synthesis.md]]`: Process for consilience framework synthesis. * `[[special/EXTRACT-ResearchQuestions.md]]`: Process for extracting research questions. --- **How to Use This System:** 1. **Start with `00-EXPLORE-ProjectIdea.md`** if your idea is still forming, or directly with `01-INITIATE-Project.md` if you have a clear project concept. 2. The AI will guide you through each phase, proposing content and actions, and asking for your confirmation or specific input via yes/no questions. 3. When the AI needs to transition to a new core process (e.g., from Planning to Execution), it will explicitly ask you to provide the next template file (e.g., "Please provide the `03-EXECUTE-Task.md` template."). 4. Supporting and specialized templates will generally be invoked by the AI as sub-processes within the core workflow, based on the project plan or your instructions. You may be asked to provide these templates if they are new or updated. 5. Key project data (Charter, Plan, task outputs, logs, etc.) will be stored and managed by the AI within its `project_state` and can be outputted in YAML format for your records.