wf-plan

To generate a documentation-first development plan, you use a workflow that produces a spec.md and tasks.md file. This process matches relevant Wiki pages first, ensuring your implementation stays traceable to current documentation before coding begins.

Matching Wiki pages before writing code prevents implementation drift by forcing a document-first planning step. It discovers existing context and blocks planning when no related Wiki can be found, ensuring traceability for new features and bug fixes.

You cannot write a development plan without Wiki documentation because the workflow enforces Wiki-first planning. It checks for a valid documentation repository configuration and blocks the generation of spec.md and tasks.md if no related Wiki is found.

The best way to prevent duplicate active changes is to enforce slug uniqueness during the document-first planning step. The workflow validates repository types and blocks planning if an active change with the same slug already exists.

Automatic Wiki search works by scanning your documentation repository and matching relevant pages using confidence thresholds. When planning a bug fix, it automatically retrieves context or uses a manually provided Wiki reference to generate traceable output files.

Documentation-first planning supports generating tasks in different languages by writing the plan outputs into the active changes path using the configured language. This ensures the generated spec.md and tasks.md match your project's language settings.