Market Foundation Todos S01-BATCH-04: Batch Discussion 4/8

by Alex Johnson 59 views

In this article, we will delve into the intricacies of the S01-BATCH-04 Stage-01 Market Foundation todos, specifically focusing on batch discussion 4/8. This comprehensive guide will walk you through the tasks, requirements, and standards associated with this batch, providing a clear roadmap for successful completion. Whether you are a project manager, content creator, or team member, understanding the nuances of this process is crucial for contributing effectively.

📋 Task Overview

At the heart of this discussion lies a well-defined set of tasks outlined in the todo/Stage-01_Market-Foundation.todos.md file. This document serves as the central repository for all action items related to this stage of the project. Specifically, we are dealing with Task ID S01-BATCH-04, which encompasses a total of 5 TODO items. Understanding the scope and nature of these tasks is paramount for effective execution. Each task is designed to build upon the previous one, creating a cohesive and comprehensive foundation for the market strategy.

File Location and Identification

The primary reference point for this batch is the todo/Stage-01_Market-Foundation.todos.md file. This Markdown file contains a detailed list of all tasks, their descriptions, and associated metadata. Locating this file is the first step in understanding the scope of the work. The Task ID, S01-BATCH-04, further helps in identifying the specific set of tasks that fall under this batch. Keeping this identification clear ensures that everyone on the team is aligned and working on the correct set of objectives. This careful attention to file location and identification prevents confusion and duplication of effort, ultimately contributing to a more efficient workflow.

Number of TODOs

Within this batch, there are a total of 5 TODO items. This number provides a quick overview of the workload and helps in planning resources and timelines. Each TODO represents a distinct deliverable or action item, and their successful completion is essential for the overall progress of the project. Knowing the number of tasks allows for better prioritization and allocation of resources. This numerical understanding is crucial for project managers to ensure that the team is neither overwhelmed nor underutilized, fostering a balanced and productive environment.

🎯 Execution Requirements

The execution of these tasks is governed by a strict set of guidelines, meticulously detailed in the .github/copilot-instructions.md file. This document outlines the Unified Automated Pipeline (The Unified Loop), a step-by-step process designed to ensure consistency, quality, and efficiency. Adhering to these requirements is not merely a suggestion but a mandatory aspect of the workflow. Let's break down each stage of this pipeline to understand the specific actions required.

1. Scan

The initial phase involves a thorough scan of the relevant information. This includes:

  • Reading the TODO File: The first step is to read the todo/Stage-01_Market-Foundation.todos.md file in its entirety. This provides a comprehensive understanding of the tasks at hand.
  • Locating Specific TODO Items: Identify the TODO items that fall under the S01-BATCH-04 Task ID. This ensures that the focus is on the correct set of tasks.
  • Reading Task Details and Metadata: Carefully review the task descriptions, requirements, and metadata associated with each TODO item. This provides context and clarity.

This scanning process is fundamental to laying the groundwork for successful task completion. It ensures that all team members are on the same page and have a clear understanding of what is expected. By systematically gathering and reviewing the necessary information, the team can avoid misunderstandings and potential errors in the subsequent stages.

2. Expert Council & Think

This stage emphasizes collaboration and critical thinking. A three-person expert panel is assembled, comprising:

  • The Principal: The individual primarily responsible for the task.
  • A Business Advisor: An expert in market dynamics and business strategy.
  • A Risk Assessor: A professional who can identify potential risks and challenges.

This expert panel engages in a series of activities, including:

  • Retrieving Relevant Files: Access and review relevant documents, such as the Project-Bible.md, which contains overarching project guidelines and information.
  • Conflict Check: Assess whether new ideas or approaches conflict with existing project parameters or guidelines.
  • Value Assessment: Evaluate the potential value of each task in relation to the project's North Star Metrics (key performance indicators).
  • In-Depth Exploration: Explore all possible branches and details related to the tasks, ensuring a comprehensive understanding.

The 'Council & Think' phase is crucial for ensuring that the tasks align with the overall project goals and are executed in a thoughtful and strategic manner. By bringing together diverse expertise, the panel can identify potential issues, generate innovative solutions, and make informed decisions.

3. Plan

With a clear understanding of the tasks and objectives, the next step is to develop a detailed plan. This involves:

  • Determining Output Paths: Identify the specific directory where the completed work will be saved (e.g., archives/Stage-01_*/{Filename}.md).
  • Identifying Dependent Files: Determine if any files or resources are required to complete the tasks.
  • Deciding on Project-Bible.md Updates: Assess whether the Project-Bible.md file needs to be updated with any new information or insights gained during the task execution.

Planning is essential for organizing the workflow and ensuring that all necessary resources are available. By clearly defining the output paths and dependencies, the team can streamline the execution process and avoid last-minute roadblocks. This proactive approach to planning contributes to a smoother and more efficient workflow.

4. Draft

This is the production phase, where the actual work is created. The key requirements for this stage include:

  • Detailed and Complete Content: Produce thorough and comprehensive content that addresses all aspects of the task.
  • Eliminating AI-like Language: Avoid using phrases commonly associated with AI-generated text (e.g., "however," "obviously," "at this moment").
  • Show, Don't Tell: Use descriptive language and examples to convey information effectively.
  • Short Sentences: Maintain clarity and readability by using concise sentences.
  • Commercial Hooks: Include commercial hooks every 2000 words to maintain audience engagement.

The Draft stage is where the ideas and plans are translated into tangible outputs. By adhering to the guidelines for content creation, the team can ensure that the deliverables are of high quality and effectively communicate the intended message. The emphasis on detailed content, clear language, and commercial hooks contributes to a final product that is both informative and engaging.

5. Verify

Quality assurance is paramount. This stage involves a thorough self-review, including:

  • Meeting Acceptance Criteria: Assess whether the work meets the defined acceptance criteria.
  • Human-Like Writing: Evaluate whether the content reads as if it were written by a human expert.
  • Immediate Redo: If the work does not meet the required standards, immediately iterate and improve the draft.

The Verification stage is critical for ensuring that the deliverables meet the required standards and are of the highest quality. By critically evaluating their own work, team members can identify areas for improvement and refine their outputs. This iterative process of self-review and revision is essential for producing exceptional results.

6. Commit

The final stage involves:

  • Saving Files: Save the completed work to the designated output path.
  • Updating Project-Bible.md: If any new settings, foreshadowing, or characters were introduced, update the Project-Bible.md accordingly.
  • Updating Risk-Ledger.md: If any unresolved issues were identified, update the Risk-Ledger.md.
  • Checking TODOs: Mark the TODO items as completed by changing - [ ] to - [x].

The Commit stage marks the culmination of the task execution process. By ensuring that all files are saved, documents are updated, and TODO items are checked, the team can maintain a clear and accurate record of progress. This final step is essential for maintaining organization and accountability within the project.

⚠️ Absolute Hard Constraints

There are several non-negotiable constraints that must be adhered to throughout the task execution process:

  1. Atomic Execution: Each TODO item must be completed independently. Batch completion is strictly prohibited.
  2. Closed-Loop Delivery: Every task must result in a tangible output. "To be supplemented" or similar placeholders are not acceptable.
  3. Deep Thinking: Superficial or cursory work is unacceptable. The full computational power of AI should be leveraged.
  4. Mandatory Chinese: All outputs must be in Simplified Chinese.

These hard constraints are designed to ensure the integrity and quality of the work. By adhering to these guidelines, the team can maintain a high level of consistency and accountability throughout the project. The emphasis on atomic execution, closed-loop delivery, deep thinking, and mandatory Chinese ensures that the deliverables are both comprehensive and culturally appropriate.

📦 Delivery Standards

The following standards must be met for each task:

  • TODO Checked: The TODO item must be marked as completed in the todo/Stage-01_Market-Foundation.todos.md file.
  • Output Archived: The completed work must be saved to the designated archives/ directory.
  • Settings Updated: The Project-Bible.md file must be updated with any new settings or information.
  • PR Contains Self-Inspection Checklist: The Pull Request (PR) must include a checklist confirming that the work has been self-reviewed.
  • **PR Description Includes Fixes #issue_number}** The PR description must include the statement "Fixes #{issue_number", referencing the relevant issue number.

These delivery standards provide a clear and measurable set of criteria for evaluating the success of each task. By adhering to these standards, the team can ensure that all deliverables are complete, accurate, and properly documented. The emphasis on TODO checking, output archiving, setting updates, self-inspection, and PR descriptions contributes to a transparent and accountable workflow.

📚 Reference Files

The following files serve as important references for this batch:

  • .github/copilot-instructions.md
  • todo/Stage-01_Market-Foundation.todos.md
  • Stages/Stage-01_*.md
  • Project-Bible.md (will be automatically created if it doesn't exist)
  • Risk-Ledger.md (will be automatically created if it doesn't exist)

These reference files provide essential context and guidance for the task execution process. By familiarizing themselves with these documents, team members can ensure that their work aligns with the overall project goals and guidelines. The inclusion of instructions, TODO lists, stage documentation, a project bible, and a risk ledger provides a comprehensive framework for successful task completion.

💡 Tips

  • If you encounter a non-blocking issue, make a decision based on the setting library and record it in the log.
  • Each TODO is an independent creative act that requires a complete six-step cycle.
  • Don't skimp on Tokens. Be as detailed as possible during the #think and #draft stages.

These tips offer practical guidance for navigating the task execution process. By encouraging independent decision-making, emphasizing the cyclical nature of the workflow, and advocating for detailed documentation, these tips aim to foster a proactive and efficient work environment. The recommendation to leverage Tokens during the thinking and drafting stages highlights the importance of thorough planning and content creation.

📋 Task Details

Let's now dive into the specific tasks included in this batch. Each task has a unique identifier, a designated expert, a detailed description, specific output requirements, and clear acceptance criteria.

S01-CA-016 Creative Direction C - Category Selection

  • Responsible Experts: CA (Chief Architect) + MA (Market Analysis)
  • Task Description: Select a category/theme for Creative Direction C that is different from A and B.
  • Output Requirements:
    • Determine the category (e.g., Eastern Fantasy, Urban Powers, Historical Fiction, Space Science Fiction, etc.).
    • Explain the reasons for the selection (market capacity, competitive intensity, personal advantages).
    • Output to the "Scheme C" section of archives/Stage-01_Market-Foundation/Creative-Concepts.md.
  • Acceptance Criteria: The selection rationale should be no less than 300 words and include data support.

This task is crucial for establishing a unique and compelling direction for Creative Direction C. By requiring a category selection different from A and B, the task encourages exploration of diverse themes and genres. The output requirements ensure that the selection is well-reasoned and supported by market data. The acceptance criteria set a clear benchmark for the quality and depth of the rationale.

S01-CA-017 Creative Direction C - Core Creative Design

  • Responsible Experts: CA (Chief Architect) + VE (Fun Point Engineer)
  • Task Description: Design the complete core creative for Scheme C.
  • Output Requirements:
    • A one-sentence selling point (within 30 characters, including: identity + dilemma + plug-in + goal).
    • Protagonist prototype (identity, personality, core desire, fatal weakness).
    • Plug-in/Golden Finger design (acquisition method, core ability, usage cost, limit).
    • Core conflict (protagonist vs. who? Why must they fight?).
    • Worldview foundation (era background, power system prototype).
    • Add to the "Scheme C" section of archives/Stage-01_Market-Foundation/Creative-Concepts.md.
  • Acceptance Criteria: A total of no less than 1500 words, logically self-consistent.

This task delves into the core elements of Creative Direction C, focusing on character development, conflict, and world-building. The one-sentence selling point is designed to capture the essence of the concept in a concise and compelling manner. The detailed output requirements ensure that all critical aspects of the creative are thoroughly explored. The acceptance criteria emphasize both the quantity and quality of the content, ensuring a logically consistent and well-developed concept.

S01-VE-018 Creative Direction C - Golden Three Chapters Scene Design

  • Responsible Experts: VE (Fun Point Engineer) + SD (Scene Director)
  • Task Description: Design the key scenes for the opening golden three chapters of Scheme C.
  • Output Requirements:
    • Chapter 1 scene: Conflict outbreak point (What crisis is the protagonist in?).
    • Chapter 2 scene: Plug-in debut (How to use the Golden Finger? What is the effect?).
    • Chapter 3 scene: Slap/Reversal (How to shock the enemy/audience?).
    • Each chapter scene includes: location, characters, conflict, emotional high point.
    • Add to the "Scheme C" section of archives/Stage-01_Market-Foundation/Creative-Concepts.md.
  • Acceptance Criteria: A total of no less than 1000 words for 3 scenes, with a sense of picture.

This task focuses on the crucial opening scenes of Creative Direction C, aiming to captivate the audience from the outset. The output requirements guide the design of each scene, emphasizing conflict, character development, and emotional impact. The acceptance criteria ensure that the scenes are not only well-written but also visually engaging, creating a vivid and immersive experience for the reader.

S01-PM-019 Three-Scheme Evaluation and Decision

  • Responsible Experts: PM (Project Manager) + MA (Market) + CA (Architecture) + MS (Marketing)
  • Task Description: Comprehensively evaluate the three schemes A/B/C and select the final direction.
  • Output Requirements:
    • Evaluation dimension 1: Commercial potential (market capacity, competitive intensity, monetization ability) Score 1-10 points.
    • Evaluation dimension 2: Scalability (Can you write 4 million words? Is it easy to get tired?) Score 1-10 points.
    • Evaluation dimension 3: Degree of differentiation (degree of differentiation from competing products) Score 1-10 points.
    • Evaluation dimension 4: Execution difficulty (setting complexity, world view construction cost) Score 1-10 points.
    • Evaluation dimension 5: Personal interest/advantage (Are you good at it? Are you enthusiastic?) Score 1-10 points.
    • Comprehensive decision: select the winning plan and explain the reason.
    • Output to archives/Stage-01_Market-Foundation/Concept-Evaluation.md.
  • Acceptance Criteria: Includes a complete scoring table, and the decision rationale is no less than 500 words.

This task is a critical decision-making point in the project, requiring a comprehensive evaluation of the three creative schemes. The output requirements provide a structured framework for the evaluation, considering factors such as commercial potential, scalability, differentiation, execution difficulty, and personal interest. The acceptance criteria ensure that the evaluation is thorough and well-reasoned, leading to an informed decision about the final direction of the project.

S01-CA-020 One-Sentence Selling Point Refinement

  • Responsible Experts: CA (Chief Architect) + MS (Marketing Expert)
  • Task Description: Refine the selling point of the winning plan into one sentence (for book title, introduction, promotion).
  • Output Requirements:
    • Core hook within 30 characters.
    • Must include: protagonist identity + core dilemma + unique plug-in + ultimate goal.
    • Pass the "3-second test" (show to 10 strangers, at least 7 are willing to click).
    • Output to archives/Stage-01_Market-Foundation/High-Concept-Document.md.
  • Acceptance Criteria: Complies with the 30-character limit, includes four elements, and passes the test.

This task focuses on crafting a compelling and concise selling point for the winning creative scheme. The output requirements emphasize the key elements that should be included in the one-sentence hook, such as the protagonist's identity, dilemma, plug-in, and goal. The acceptance criteria ensure that the hook is not only well-written but also effective in capturing attention and generating interest. The "3-second test" provides a practical measure of the hook's effectiveness.

Conclusion

Understanding and adhering to the guidelines and requirements outlined in this article is crucial for the successful completion of the S01-BATCH-04 Stage-01 Market Foundation todos. By following the Unified Automated Pipeline, adhering to the hard constraints, and meeting the delivery standards, team members can contribute effectively to the project's goals. Each task, with its unique requirements and acceptance criteria, plays a vital role in building a solid foundation for the market strategy. Remember to consult the official documentation for further details and clarification on market foundation principles.