{
  "markdown": "# Agile Agentic Framework\n\nThis README is the entry point for people who use or develop the framework. AI agents use `AGENTS.md` as their self-contained repository entry point and load relevant skills as needed; they do not need this README as operating input.\n\nThis repository defines runtime-neutral agent roles and a shared skill catalog for an agentic Scrum system.\n\nFor an illustrated guide to framework use, architecture, agentic principles, lifecycle, extensions, evaluations, and design rationale, start with the [OKF documentation bundle](docs/index.md). The documentation is for people and is not operating input for agents.\n\n## Structure\n\n- `agents/`: one runtime-neutral manifest per agent.\n- `skills/agent-core-skills/`: mandatory role contracts and role specializations.\n- `skills/`: process, cross-role, and other optional skills such as bootstrap, Sprint cycle, and OKF.\n\nA skill needs only `skills/<skill-name>/SKILL.md`. Add scripts, references, or assets only when they are used. Runtime-specific UI metadata such as `agents/openai.yaml` is intentionally omitted unless a concrete integration requires it.\n\nThe Product Owner is defined by `agents/product-owner/agent.yaml`. Programmer and Tester agents combine the shared Scrum Developer contract in `skills/agent-core-skills/developer-core/` with their specialization in `skills/agent-core-skills/programmer-core/` or `skills/agent-core-skills/tester-core/`. The runtime host uses `skills/manage-role-interaction/` and `skills/run-sprint-cycle/` for conversation and lifecycle mechanics without acting as a Scrum role. The Scrum Master uses `skills/agent-core-skills/scrum-master-core/` on demand for facilitation, impediments, Scrum guidance, and improvement. Product-specific stakeholder agents can reuse `skills/agent-core-skills/stakeholder-core/` while remaining outside the Scrum Team. All agents can discover shared capabilities such as `skills/okf/`.\n\n## Start a product workspace\n\nUse the bootstrap skill to create a separate, Git-ready workspace for one product:\n\n```bash\npython3 skills/bootstrap-product-development/scripts/bootstrap.py \"My Product\" --parent ../\n```\n\nThis creates `product-development-my-product/` with a human and agent entry point, a `product-code/` area, initial OKF artifacts, a Product Backlog, Sprint and Increment Documentation areas, and a `.aafe/` extension layer. Keep product knowledge and product-specific framework changes there; do not modify this base framework for one product's needs.\n\nProduct Vision and the current Product Goal live under `artefacts/product-backlog/` with its index. For a new Product Vision, the Product Owner offers Roman Pichler's simple and extended Product Vision Board, guides the human through it field by field, and then uses the confirmed board to establish the next Product Goal. PBI files begin under `artefacts/product-backlog/items/`. Sprint Planning stores the Sprint Goal at `sprint-backlog/sprint-goal.md` and moves selected PBI files beside it. Done PBIs and resolved Bugs remain there as the completed Sprint record; unfinished work is moved back to the Product Backlog for Product Owner ordering.\n\n## Test and improve the framework\n\nFramework development and product development may alternate during a trial, but changes remain separated:\n\n- Reusable framework defects and improvements belong in this repository.\n- Product-specific framework extensions and overrides belong under the product repository's `.aafe/` directory.\n- Product knowledge and Product Code belong only in the product repository.\n\nValidate and version each repository independently so a product experiment cannot silently change the base framework.\n\nBehavioral changes to agent manifests, skills, and agent instructions are checked with the lightweight, runtime-neutral evaluations under [`evals/`](evals/README.md). Evaluation cases stay separate from the productive instructions they test. Change authors provide the relevant evidence, critical behavior is reviewed independently when practical, and the human maintainer remains responsible for the merge decision. Resource savings count as improvements only when the candidate continues to pass the same quality criteria as the unchanged baseline.\n\n## Validation\n\nInstall the validator's single dependency and validate an OKF knowledge bundle:\n\n```bash\npython3 -m venv .venv\n.venv/bin/python -m pip install -r skills/okf/scripts/requirements.txt\n.venv/bin/python skills/okf/scripts/validate_okf.py path/to/bundle\n```\n\nAI-agent operating instructions are maintained separately in [AGENTS.md](AGENTS.md). People may inspect that file when reviewing or developing agent behavior, but it is not required for ordinary framework use.\n\n## License\n\nExcept for the material identified below, this project is licensed under the [MIT License](LICENSE). You may use, modify, and distribute it, including for commercial purposes, provided that the copyright notice and license terms are retained as required by the license.\n\nThe adapted Product Vision Board material in [`skills/product-vision-board/SKILL.md`](skills/product-vision-board/SKILL.md) is based on the [Product Vision Board](https://www.romanpichler.com/blog/the-product-vision-board/) by Roman Pichler and is licensed under [Creative Commons Attribution-ShareAlike 4.0 International](https://creativecommons.org/licenses/by-sa/4.0/) (CC BY-SA 4.0). Generated Product Vision Board artifacts carry their own attribution and license notice.\n",
  "bytes": 5466,
  "sha": "79c040f8e3a66febfe7163f1990ea1ff26e42979605d1cfa731f5d195d85fad9",
  "repo_slug": "se-keller/agile-agentic-framework",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/okf_se_keller_agile_agentic_framework_skills_5ce1887c/readme"
}