> For the complete documentation index, see [llms.txt](https://docs.k9rockettech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.k9rockettech.com/testing-and-documentation/internal-dev-log-template.md).

# Internal Dev Log Template

The Dev Log is our internal daily journal system to both accelerate development and make ourselves a better engineer! The goal isn't a draggy and boring log of overly technical jargons, it's a quick way to jot down progress and issues

## Dev Log Format Overview

**00/00/22** ( Date, obviously)

**Progress Location:** Location of where development was focused on, can range from general assembly as a whole to a specific part.

**Progress Details:** A quick recap of what

**Findings:** A list of new things found and learned per daily development cycle

**Links:** A Library of links to parts, additional resources, and reference material relevant to the days development cycle

**Images & Notes:** A Library of images showing progress and

## Dev Log Template

*(Copy Paste into Dev Log for each day)*

**00/00/2023**

**Progress Location:**

**Progress Details:**

**Findings:**

**Links:**

**Images & Notes:**


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.k9rockettech.com/testing-and-documentation/internal-dev-log-template.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.