ineersa/hatfield-ext-task-workflow

Task workflow extension for Hatfield (native port of pi task-workflow).

v0.0.7 2026-08-05 00:40 UTC

Requires

• php: >=8.3
• helgesverre/toon: ^3.1
• ineersa/hatfield-extension-api: @dev

MIT

Published on Packagist.org on 2026-08-05 16:22 UTC

README

Native Hatfield port of the pi task-workflow extension. It registers task board tools, slash commands, and system prompt guidance for the external task workflow.

This package requires ineersa/hatfield-extension-api for Ineersa\Hatfield\ExtensionApi\* contracts. In this monorepo that dependency is a path repository; released consumers install the published API package.

Runtime loading

ExtensionManager requires .hatfield/extensions/vendor/autoload.php to autoload project extension classes. After cloning or pulling this repository (or updating extension packages), refresh both autoload contexts from the repository root:

composer install
composer install -d .hatfield/extensions

• Root composer install — updates the host vendor/autoload.php when root composer.json maps extension namespaces (e.g. for tests and Castor QA).
• composer install -d .hatfield/extensions — installs path packages and creates .hatfield/extensions/vendor/autoload.php, which Hatfield loads at startup when extensions.enabled lists this extension.

If dependencies are already installed and only autoload maps changed, composer dump-autoload at the root is sufficient for (1); you still need (2) whenever .hatfield/extensions/vendor/ is missing or stale.

Enable Ineersa\HatfieldExt\TaskWorkflow\TaskWorkflowExtension in .hatfield/settings.yaml under extensions.enabled, then start a new Hatfield session — extensions register at startup; an existing TUI session will not show new tools or slash commands until restart.

See docs/settings.md (extensions.enabled, extensions.settings.task_workflow) for configuration.