skills.rest
mica-agent
mica-agentOFFICIAL
Explore all skills by this author →
GitHub

participate-fully

Assess Mica canvas changes and select the appropriate response action.

Updated May 21, 2026
Search Tags:#tool orchestration#architecture alignment#workflow guardrails#documentation upkeep#mica canvas#turn awareness
One-click install
npx skills add https://github.com/mica-agent/mica-solar-system --skill participate-fully
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: participate-fully
Source: https://github.com/mica-agent/mica-solar-system/tree/main/.qwen/skills/participate-fully
Command: npx skills add https://github.com/mica-agent/mica-solar-system --skill participate-fully

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps an AI participant reliably interpret what changed on a Mica canvas between turns and choose the right next action instead of replying without context or missing required updates.

Core Features & Use Cases

  • Change-aware participation: Reads the “Since your last turn” section and classifies changes as user-driven, external, or residue to guide response strategy.
  • Design-memory routing: Loads canvas/decomposition.md (when present) to align with the project’s established architecture before touching code or architecture.
  • Safe action selection: Uses explicit step logic to decide whether to answer, reconcile contradictions, update docs, run tools, or flag follow-ups—while avoiding build-trigger mistakes.

Quick Start

Use participate-fully at the start of every turn to read the “Since your last turn” section and decide whether to acknowledge, ask, update documentation, or invoke tools based on what changed.

Frequently Asked Questions about participate-fully

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

FAQPage Schema
How do I assess Mica canvas changes between turns to choose the right AI response?▼

To assess Mica canvas changes between turns, read the “Since your last turn” section to classify updates as user-driven, external, or residue, which guides whether to answer, reconcile contradictions, or update documentation.

How does architecture alignment work when updating files on an iterative canvas?▼

Architecture alignment works by loading the canvas/decomposition.md file when present, ensuring the AI participant references established project architecture before touching code or making structural edits.

What's the best way to prevent build-trigger mistakes from non-build canvas events?▼

The best way to prevent build-trigger mistakes is applying workflow guardrails that use explicit step logic to avoid tool invocations or broad edits triggered by non-build events on the canvas.

When do I need documentation upkeep during iterative canvas work?▼

You need documentation upkeep during iterative canvas work when the change assessment identifies contradictions or completed updates, requiring the participant to reconcile files and flag follow-ups.

Does tool orchestration support external process updates on a Mica canvas?▼

Tool orchestration supports external process updates by classifying these changes through turn awareness, enabling the participant to safely route actions and invoke tools only when required safety checks pass.

Related Skills

Explore More Product & Management Skills→
duonghuan2122000duonghuan2122000
1

openspec-apply-change

Guide OpenSpec change selection, schema inspection, and incremental task implementation.

Community
Intermediate
ForgePlanForgePlan
3

refine

Refine design documents by resolving contradictions and updating CONTEXT.md and ADRs.

Official
Advanced
mica-agentmica-agent

grow-canvas

Propose new Mica canvas cards from conversation signals.

Official
Basic
stravineststravinest

codebase-update

Update .codebase documentation to reflect recent code changes.

Community
Basic