Repository navigation
Gemba 0.1.0
The first release: the whole cycle of a task, from a tasks repo that gemba init
creates to the report of a period.
Added
gemba init, which makes a folder a tasks repo, and thegemba-initskill, the
guided first configuration.gemba.yaml, the gemba config: workstreams with their prefixes, typed metadata
fields (text,number,boolean,date), agent providers, the IDE command, the
organization, the repositories folder, andcontextandrulesper process, at the
top level and per workstream;gemba config checkandgemba config show, and the
gemba-configskill that holds the reference of every key.gemba create,gemba list,gemba set,gemba markandgemba archive, each with
its skill: the frontmatter of a task is written by commands only, refs are never
reused, and listings and reports read every task file and report the invalid ones.gemba harness launch,note,resolveandremove: the harness of a run, its own
git repository with the guide of the agent, the filed notes and their approval gate
for actions outside the harness.gemba worktree add,listandremove: git worktrees of the organization's
repositories inside a harness, each on the local branch of the run, never pushed
under its own name.gemba recordand thegemba-reportskill: the update of a day written into the
task from a draft, and the report of a day, a week or a month, with every count and
sum taken fromgemba report.gemba skills update: the skills ship with the package and are written into the
tasks repo and into each harness for every agent provider declared, with their
provenance, so an upgrade refreshes them and a hand edit is kept.