> For the complete documentation index, see [llms.txt](https://docs.launchboard.app/cxd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.launchboard.app/cxd/project-robotics/project-instructions/2-design-and-build-solution.md).

# 2 DESIGN & BUILD SOLUTION

![](https://4071112868-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LDgX-RpDDd3FfQb3yBa%2F-LSGp06FZKaTZRe1peej%2F-LSGppJ_j2LX1CEHjjXj%2Fphase-2-process.png?alt=media\&token=d57e9b3f-babc-460e-8383-71d8814d53a7)

Create a schedule to design and develop your solution, based on the available time and resources. Define design specifications for your robot prototype, as well as for your fully-functional robot concept. Use a paper prototype of your task scenarios to evaluate them with external users, and make any necessary refinements. Construct your robot's demonstration environment, and program your robot prototype to perform its tasks. Internally test your robot solution to verify its effectiveness, measure its performance, and identify any issues. Create a product website and demo video to help explain and show your robot solution to others. Use your project schedule to continually track your team's progress, in order to finish on time. Demonstrate your solution to the class.

This phase of the project will require about 5-7 weeks to complete. Your teacher will identify the specific deadline(s) for the task assignments.

| Task                                                                                                                                       | Estimated Time | ✓ | ✓+ |
| ------------------------------------------------------------------------------------------------------------------------------------------ | -------------- | - | -- |
| [2.1 Project Schedule](/cxd/project-robotics/project-instructions/2-design-and-build-solution/2.1-project-schedule.md)                     | 1 hour         |   |    |
| [2.2 Robot Specifications](/cxd/project-robotics/project-instructions/2-design-and-build-solution/2.2-robot-specifications.md)             | 3 hours        |   |    |
| [2.3 Paper Prototype Evaluation](/cxd/project-robotics/project-instructions/2-design-and-build-solution/2.3-paper-prototype-evaluation.md) | 3 hours        |   |    |
| [2.4 Robot Demo Environment](/cxd/project-robotics/project-instructions/2-design-and-build-solution/2.4-robot-demo-environment.md)         | 5 hours        |   |    |
| [2.5 Program Robot Prototype](/cxd/project-robotics/project-instructions/2-design-and-build-solution/2.5-program-robot-prototype.md)       | 10-20 hours    |   |    |
| [2.6 Product Website](/cxd/project-robotics/project-instructions/2-design-and-build-solution/2.6-product-website.md)                       | 5 hours        |   |    |
| [2.7 Robot Demo Video](/cxd/project-robotics/project-instructions/2-design-and-build-solution/2.7-robot-demo-video.md)                     | 2 hours        |   |    |
| [**2.8 Solution Presentation**](/cxd/project-robotics/project-instructions/2-design-and-build-solution/2.8-solution-presentation.md)       | 2 hours        |   | .  |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.launchboard.app/cxd/project-robotics/project-instructions/2-design-and-build-solution.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.