@amsterdamdatalabs/enact-extensions 0.1.10 → 0.1.24

package/extensions/enact-operator/skills/wiki/SKILL.md

@@ -1,41 +0,0 @@
----
-name: wiki
-description: "Wiki-style reference lookup delegated to the enact-wiki provider. Use when the operator wants durable project documentation or knowledge retrieval."
----
-
-# Wiki
-
-## Purpose
-Provides access to the project's durable wiki and knowledge base by delegating to the enact-wiki provider. Operator orchestrates the request and receives the result; it does not re-implement wiki storage or retrieval. Operator-side artifacts produced by research or analysis can be persisted to the wiki via this skill.
-
-## Use When
-- The operator wants to look up a documented decision, design, or reference
-- Research findings from `$autoresearch-goal` should be persisted as a durable wiki entry
-- The operator asks "does the wiki have anything on X?"
-
-## Workflow
-1. Identify the query or document to persist.
-2. Delegate the operation to the enact-wiki provider using its wiki MCP tools.
-   - For a lookup: invoke the enact-wiki wiki query tool with the search term.
-   - For a write: invoke the enact-wiki wiki add tool with the content and title.
-   - For a list: invoke the enact-wiki wiki list tool.
-   - For a read of a specific entry: invoke the enact-wiki wiki read tool with the entry identifier.
-3. If the operation returns content, present it directly to the operator without reformatting.
-4. If persisting a Operator research artifact (e.g., `.enact/operator/research/<goalId>.md`), read the file first, then pass the content to the enact-wiki wiki add tool.
-5. Operator does not store wiki state locally. The enact-wiki provider is the canonical store.
-
-## State Contract
-- Reads: enact-wiki wiki store (via MCP tool calls), `.enact/operator/research/` files when persisting
-- Writes: enact-wiki wiki store (via MCP tool calls); no local `.enact/operator/` files written by this skill
-
-## Dependencies
-- Requires enact-wiki MCP server to be connected. If it is not available, report that to the operator and stop.
-
-## Activation
-
-When a prompt contains `$enact-operator:<skill-name>` or `$<skill-name>`, Operator's UserPromptSubmit hook records the invocation in `.enact/operator/state/skill-active.json` and adds an MCP-first context note for the agent. That note tells the agent to load/search the Enact Operator MCP namespace immediately if `operator_*` tools are not visible yet, then prefer `operator_*` tools over the `enact-operator` CLI. This skill is operator-driven — there is no durable workflow state to start automatically. The activation log gives operators and the HUD a trace of which skills were explicitly invoked.
-## Final Check
-- The query returned a result or a clear "not found" from enact-wiki
-- For writes, the enact-wiki tool confirmed the entry was saved
-- No wiki content was stored locally in `.enact/operator/` as a substitute for the enact-wiki store
-- If enact-wiki was unavailable, the operator was notified explicitly

package/extensions/enact-operator/skills/work-with-workitem/SKILL.md

@@ -1,51 +0,0 @@
----
-name: work-with-workitem
-description: "Lightweight Azure DevOps work-item delivery lane: implement and hand off; factory owns tracking and closure."
----
-
-# Work With Workitem
-
-## Purpose
-
-Use `$work-with-workitem` for operator-domain delivery tied to a single Azure DevOps work item.
-
-## Domain Boundary
-
-- operator scope is intentionally lightweight: load, isolate, implement, PR, handoff, cleanup
-- enact-factory owns CI heartbeat tracking, branch policy waits, auto-merge, and lifecycle advance to `Closed`
-- this skill must not add CI polling loops or unbounded branch-policy waiting
-
-## Azure DevOps-Only Contract
-
-- use `factory_workitem_get` and `factory_assignment_record` for work-item reads and closing notes
-- use `az repos pr create --work-items <id>` to link the PR to the work item
-- do not assume or reference GitHub APIs, GitHub Actions, GitHub checks, or GitHub branch protection primitives
-
-## Required Sequence
-
-1. `factory_workitem_get` loads the target work item and confirms readiness.
-2. `EnterWorktree` isolates the implementation workspace.
-3. Execute implementation with `$ultrawork` (or `$ralph` for simple tasks).
-4. Create atomic commits with clear work-item-linked intent.
-5. Run `az repos pr create --work-items <id>` and capture the PR URL.
-6. Call `factory_assignment_record` with a closing note that includes PR URL and commit SHA.
-7. `ExitWorktree` cleans up the isolated workspace.
-
-## Behavioral Constraints
-
-- no CI poll loop in this skill; CI heartbeat belongs to `factory_watchdog_status`
-- no merge waiting or policy-wait ownership in this skill
-- no lifecycle mutation to `Closed` from this skill
-- if PR creation fails, record failure context and exit through normal cleanup
-
-## Verification Expectations
-
-- integration target is a work item tagged `test-fixture`
-- verify PR link uses `--work-items <id>`
-- verify `factory_assignment_record` includes PR URL and commit SHA
-- verify `ExitWorktree` cleanup is executed
-- do not verify CI completion or merge here
-
-## Activation
-
-When a prompt contains `$enact-operator:<skill-name>` or `$<skill-name>`, Operator's UserPromptSubmit hook records the invocation in `.enact/operator/state/skill-active.json` and adds an MCP-first context note for the agent. That note tells the agent to load/search the Enact Operator MCP namespace immediately if `operator_*` tools are not visible yet, then prefer `operator_*` tools over the `enact-operator` CLI. This skill is operator-driven — there is no durable workflow state to start automatically. The activation log gives operators and the HUD a trace of which skills were explicitly invoked.