Instructions for LLM Agent

Welcome! This document outlines how to effectively use the Orchestatr repository to manage product documentation, feature development, and task iteration. Your primary role is to assist users by generating, maintaining, and iterating on documentation and tasks, always adhering to the established workflows.

Core Principles

1. Context is King: Always refer to existing and generated documentation (/docs, /tasks, and library_docs/) to inform your responses and actions. Do not generate information in a vacuum.
2. Follow the Workflow: Adhere strictly to the sequential nature of the 01_start directories and the purpose of other instruction files.
3. Environment Agnostic: All instructions and generated content should be in .md format, ensuring reusability across different environments and tools.
4. Iterative Development: Understand that development is iterative. Your role is to help refine and build upon existing work.

Getting Started: Choosing Your Path

This repository supports two primary development paths: building an application or building a website. The instructions/ directory contains all the necessary .md files to guide you through these processes.

Path 1: Building an Application (instructions/app/)

If the user intends to build an application, direct them to the instructions/app/ directory. The initial setup involves a sequential workflow:

Initial Application Setup (instructions/app/01_start/)

Guide the user through these .md files in the following order. Each file prompts you to generate a specific document, which should be saved in the /docs directory (or /tasks for task lists).

1. 01_create_product_brief.md: Generate a comprehensive product brief.
2. 02_create_market_user_research.md: Conduct market and user research, creating personas.
3. 03_create_feature_spec.md: Detail the application's features and functionality.
4. 04_create_design_guidelines.md: Establish design and UX guidelines.
5. 05_create_architecture.md: Define the technical architecture.
6. 06_create_metrics_risks.md: Identify success metrics and potential risks.
7. 07_create_mvp_tasks.md: Generate a task list for the Minimum Viable Product (MVP).

Crucial: After each step, ensure the generated document is saved and then refer to it in subsequent steps for consistency and context.

Ongoing Application Feature Development (instructions/app/features/)

For new features or iterations on an existing application, use these instructions:

• create-prd.md: Generate a Product Requirements Document (PRD) for a new feature.
• generate-tasks.md: Create implementation tasks based on a PRD.
• iterate-tasks.md: Manage and track progress on existing tasks.

Path 2: Building a Website (instructions/site/)

If the user intends to build a website, direct them to the instructions/site/ directory. The initial setup also follows a sequential workflow:

Initial Website Setup (instructions/site/01_start/)

Guide the user through these .md files in the following order. Each file prompts you to generate a specific document, which should be saved in the /docs directory (or /tasks for task lists).

1. 00_create_business_plan.md: Develop a business plan for the website.
2. 01_create_brief_audience.md: Create a detailed audience brief.
3. 02_create_competitor_keyword_research.md: Perform competitor and keyword research.
4. 03_create_architecture_content.md: Plan website architecture and content strategy.
5. 04_create_design_content.md: Establish design principles and content guidelines.
6. 05_create_technical_plan.md: Define the technical implementation plan.

Crucial: After each step, ensure the generated document is saved and then refer to it in subsequent steps for consistency and context.

Ongoing Website Optimization and Content Creation (instructions/site/ root)

For optimizing an existing website or creating new content, use these instructions located directly in instructions/site/:

• analyze-page.md: Analyze a specific page for UX issues and suggest improvements.
• competitor-breakdown.md: Conduct a detailed breakdown of a competitor's website.
• generate-headlines.md: Generate various headlines for content.
• iterate-tasks.md: Manage and track progress on website-related tasks.
• keyword-research.md: Perform in-depth keyword research for SEO.
• new_page.md: Generate a new page structure, including wireframe and initial copy.
• programmatic-seo.md: Develop a strategy for programmatic SEO.
• ux-audit-leadgen.md: Perform a UX audit focused on lead generation.

Supporting Documentation (library_docs/)

The library_docs/ directory contains a wealth of research and best practices across various domains. Always refer to these documents when generating new content or providing advice to ensure high-quality, informed outputs.

• copywriting/: Guides on effective copywriting, CTAs, headline formulas, etc.
• design_ux/: Principles of UX/UI design, wireframing best practices, font pairings, etc.
• seo/: Processes for keyword research, on-page SEO techniques, etc.

Generating Documents

When an instruction requires you to generate a document (e.g., a product brief, a task list), save it in the appropriate directory (/docs for general documents, /tasks for task lists). Name the files descriptively and consistently.

Maintaining a Project Timeline

To help users stay oriented, you should maintain a high-level timeline or master list of completed work and next steps. This does not need to be a detailed task list, but rather a summary of progress.

• Track Completed Items: Keep a running list of which documents have been generated (e.g., "Product Brief - Complete") and which major features have been worked on.
• Determine Next Steps: When a user asks "What's next?" or "Where are we?", consult your timeline and the project structure to determine the next logical step.
• Guide the User: Point the user to the next sequential instruction file (e.g., "The next step is to create the market and user research. You can do this by running instructions/app/01_start/02_create_market_user_research.md.") or to a relevant task file for more granular work (e.g., "The MVP tasks have been generated in /tasks/mvp_tasks.md. You can start working on those.").

Next Steps for the User

If the user asks how to get started or what to do next, guide them to choose between the "Building an Application" or "Building a Website" paths, and then instruct them to begin with the first sequential .md file in the chosen path's 01_start directory. Remind them to save generated output and refer to it for subsequent steps.