Director-Driven Development：用 AI 编码智能体做“你指挥、智能体构建”的开发文档

Documentation for Director-Driven Development, a way of working with AI coding agents: you direct, agents build, an automatic check proves every task.

Site: https://freakling.github.io/Director-Driven-Development/

The blog explains why: https://saemundsson.se/2026/10/07/director-driven-development/. The docs explain how. The three frameworks keep their own README and procedures as the source of truth, and the docs link to them:

Godot-Director: games in Godot 4
App-Director: small web, mobile and desktop apps
SaaSAllTheThings: multi-tenant B2B SaaS on Azure

Built with App-Director

This repository is built with App-Director: every change is a task in TASKS.md, design decisions live in product/, and bash tools/check.sh passes before every commit. That makes it a public example of the framework in use, and a running test that it works.

Later, the repository also becomes the orchestrator that keeps the three frameworks aligned, App-Director included, so the tool that builds this repo is aligned from it.

Working on the docs

The site is built with MkDocs and the Material theme. Pages are Markdown in docs/; the navigation is in mkdocs.yml; the look follows the graphical profile in docs/assets/stylesheets/ddd.css.

pip install -r requirements.txt
mkdocs serve          # preview at http://127.0.0.1:8000
bash selftest.sh      # before every push

selftest.sh fails on:

en or em dashes in the sources;
any command or skill a framework ships that its framework page doesn't mention (it keeps clones of the three repos in .app-director/state/frameworks, refreshes them when online and reuses them offline; set FRAMEWORKS_DIR to use other clones);
broken internal links and anchors (mkdocs build --strict).

GitHub Actions runs the selftest on every push and pull request, and deploys main to GitHub Pages.

Director-Driven Development：用 AI 编码智能体做“你指挥、智能体构建”的开发文档

Built with App-Director

Working on the docs

License