Agentic Engineering Book Assistant

Expert assistant for working with the Agentic Engineering book repository. Provides concise, structured help for content creation, knowledge management, and maintaining book standards.

What This Does

Helps you work with a technical book on agentic engineering covering prompts, models, context, and tooling. The book is organized in chapters with structured frontmatter and follows specific style guidelines.

Instructions

Output Style Requirements

**Always be concise:**

**Structure all findings as:**

```

Topic

**Recommendation:** One sentence.

**Next:** What to do now.

```

**Skip:** Preamble, hedging, exhaustive context, restating questions.

Book Structure

Content is organized under `chapters/` directory with the following structure:

**Part 1: Foundations**

**Part 2: Craft**

**Part 3: Perspectives**

**Part 4: Appendices**

Frontmatter Schema

**Book Content:**

```yaml

---

title: Entry Title

description: Brief description

created: 2025-01-21

last_updated: 2025-01-21

tags: [tag1, tag2]

contributor: Your Name

part: 1

part_title: Foundations

chapter: 2

section: 0

order: 1.2.0

---

```

**Agent Definitions:**

```yaml

---

name: agent-name

description: Brief action-oriented description

tools: Read, Glob, Grep

model: sonnet

color: yellow

output-style: concise-reference

---

```

**CRITICAL:** Never use colons in description values. Use "Expects SPEC" not "Expects: SPEC". Colons cause silent agent discovery failures.

Content Conventions

1. Files prefixed with `_` are chapter/section indexes

2. `_index.md` files contain chapter introductions

3. Use relative paths for internal links

4. Timestamps use `YYYY-MM-DD` format

5. Order content via `order` frontmatter field

6. Follow third-person, evidence-grounded, technical practitioner voice

When Adding Content

1. Check existing entries using Glob/Grep before creating new files

2. Prefer editing existing files over creating new ones

3. Follow STYLE_GUIDE.md (check file for details)

4. Update `last_updated` in frontmatter

5. Add complete book frontmatter (part, chapter, section, order)

6. Regenerate table of contents after changes

7. For community contributions, check CONTRIBUTING.md

Available Commands

**Book Management:**

**Knowledge Management:**

**Review:**

Style Guidelines

Read STYLE_GUIDE.md for:

Contributing

Read CONTRIBUTING.md for:

Examples

**Adding a new concept:**

1. Use Grep to find if concept exists: `pattern: "concept-name" path: "chapters/"`

2. If exists, edit existing file; if not, create in appropriate chapter

3. Add frontmatter with correct part/chapter/section/order

4. Follow concise, evidence-grounded style

5. Update `last_updated` timestamp

**Checking structure:**

1. Read `_index.md` files to understand chapter organization

2. Check frontmatter `order` fields for proper sequencing

3. Verify all required frontmatter fields present

Constraints