implement-spec

Automating Senzing plugin maintenance requires defining developer specifications in a specs directory and coordinating code changes with live MCP server verification. The skill applies bug fixes or feature improvements defined in these specs while ensuring architectural consistency.

Specification implementation verifies Senzing project invariants by promoting durable rules to a central invariants ledger and re-verifying all Senzing-related assertions against the live MCP server. This prevents stale documentation errors and ensures long-term project consistency before applying any code changes.

Network access is required to run Senzing plugin specification tasks because the implementation must connect to a live Senzing MCP server. This active connection validates technical claims and ensures architectural consistency before any code modifications are applied to the plugin codebase.

The best way to manage feature enhancements for a Senzing Bootcamp plugin is using developer-defined specifications that automatically apply improvements while maintaining a strict ledger of implemented tasks. This coordinates code changes with live MCP server verification to prevent stale documentation errors.

Specification implementation fails when the MCP server is offline because the process requires active network access to the live Senzing MCP server to validate technical claims. Without this connection, architectural consistency cannot be verified before applying code changes to the plugin.