invoke

Convert development intent into governed lifecycle artifacts with mode contracts.

20|3|Updated May 14, 2026
One-click install
npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill invoke-cyberalchemyai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: invoke
Source: https://github.com/cyberAlchemyAI/Arcanum/tree/main/.claude/skills/invoke
Command: npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill invoke-cyberalchemyai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform vague development intent into governed, observable artifacts that define how to proceed across lifecycle stages, ensuring clarity, ownership, and auditable outcomes.

Core Features & Use Cases

  • Governance-first translation: converts intent into define, design, plan, handoff, and refresh workflows with clear mode contracts.
  • Artifact orchestration: produces tangible outputs and structured handoffs between lifecycle stages, with traceability anchors.
  • Observability and gates: provides observability signals, validation surfaces, and risk-aware routing to owners.

Quick Start

Provide your initial development intent and target artifact type to generate a governance-ready artifact map for exploration.

Frequently Asked Questions about invoke

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn vague development intent into governed artifacts?

To turn development intent into governed artifacts, define your objective, target artifact type, and scope boundaries so the system can propose appropriate modes and generate an evidence-backed plan with validation considerations.

What is the best way to structure lifecycle handoffs between development stages?

Structuring lifecycle handoffs requires artifact orchestration to produce tangible outputs with traceability anchors, ensuring clear ownership and auditable outcomes between stages like define, design, plan, and refresh.

How do I set up validation gates and observability for software development workflows?

Setting up validation gates and observability for development workflows involves risk-aware routing to owners, providing observability signals and validation surfaces to monitor governance across lifecycle stages.

Can I use mode contracts to manage development scope and constraints?

Yes, you can use mode contracts to manage development scope and constraints by defining boundaries upfront, allowing the system to surface an evidence-backed plan with required inputs and validation considerations.

When should I use a governance-first workflow for software engineering artifacts?

A governance-first workflow should be used when transforming intent into observable artifacts, ensuring clarity, ownership, and auditable outcomes across lifecycle stages like define, design, plan, handoff, and refresh.

What inputs do I need to generate an artifact map for development exploration?

To generate an artifact map for exploration, provide your initial development intent and target artifact type to receive a governance-ready map with mode contracts and required inputs.