Skip to content

Overview

These documents describe how individual Dapsman workflows are designed and implemented.

Each one starts life as a planning document — part work-item spec, part implementation guide — and graduates here once the feature is stable. At that point the implementation notes become background context and the focus shifts to how the workflow behaves and why it’s designed the way it is.

If a workflow is being actively changed, its doc may temporarily read like a planning doc again while the work is in flight.

Not every workflow has a dedicated doc yet, mainly because the pattern of saving and promoting Claude planning sessions as documentation is new. For a complete list of available commands and their flags, see CLI Commands.