Technical Implementation Plan

Detail the architecture, dependencies, and steps required to implement a project.

View Source YAML

---
name: Technical Implementation Plan
version: 0.1.0
description: Detail the architecture, dependencies, and steps required to implement a project.
metadata:
  domain: technical
  complexity: medium
  tags:
  - software-engineering
  - sdlc
  - technical
  - implementation
  - plan
  requires_context: false
variables:
- name: architecture_overview
  description: The architecture overview to use for this prompt
  required: true
- name: data_models
  description: The data or dataset to analyze
  required: true
- name: technology_choices
  description: The technology choices to use for this prompt
  required: true
model: gpt-4
modelParameters:
  temperature: 0.2
messages:
- role: system
  content: 'You are a Principal Software Architect. Your job is to create a detailed, risk-averse Technical Implementation
    Plan that ensures scalability, security, and maintainability.


    Your plan must be actionable, specific, and technically rigorous. Avoid generic advice.'
- role: user
  content: 'Create a comprehensive Technical Implementation Plan based on the following inputs:


    <architecture_overview>

    {{architecture_overview}}

    </architecture_overview>


    <technology_choices>

    {{technology_choices}}

    </technology_choices>


    <data_models>

    {{data_models}}

    </data_models>


    Review the inputs carefully. Then, generate a plan covering:

    1. Define modules, services, and overall architecture.

    2. List the libraries, frameworks, and tools to use.

    3. Describe all required data models with fields and constraints.

    4. Specify business logic and rules in clear terms.

    5. Identify dependencies, risks, and proposed solutions.

    6. Outline step-by-step implementation for each feature or service.


    Constraint: Iterate the plan internally to address edge cases before outputting.


    Output format:

    Strictly follow this Markdown structure:

    # Technical Implementation Plan

    ## 1. Architecture Breakdown

    ...

    ## 2. Libraries and Tools

    ...

    ## 3. Data Models & Specifications

    ...

    ## 4. Business Logic & Rules

    ...

    ## 5. Dependencies & Risk Analysis

    ...

    ## 6. Implementation Steps

    ...'
testData:
- vars:
    architecture_overview: A RESTful API for a collaborative To-Do list application allowing users to create lists, share
      them, and assign tasks.
    technology_choices: Python, FastAPI, PostgreSQL, Redis, Docker.
    data_models: User (id, email, password_hash), TaskList (id, owner_id, title), Task (id, list_id, title, status, assignee_id),
      Comment (id, task_id, user_id, content).
  expected: Markdown sections for Architecture Breakdown, Libraries and Tools, Data Models & Specifications, Business Logic
    & Rules, Dependencies & Risk Analysis, and Implementation Steps.
evaluators:
- name: Valid Header Structure
  regex:
    pattern: (?m)^# Technical Implementation Plan
- name: Architecture Section Exists
  regex:
    pattern: (?m)^## 1\. Architecture Breakdown
- name: Risk Analysis Section Exists
  regex:
    pattern: (?m)^## 5\. Dependencies & Risk Analysis