act-advice-phase

Gathers and logs stakeholder advice into an assets/advice-log-template.yaml file.

2|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/Community-Chests/neos-operating-system --skill act-advice-phase-community-chests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: act-advice-phase
Source: https://github.com/Community-Chests/neos-operating-system/tree/main/neos-core/layer-03-act-engine/act-advice-phase
Command: npx skills add https://github.com/Community-Chests/neos-operating-system --skill act-advice-phase-community-chests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Automatically coordinates and records stakeholder input during the ACT advice phase, ensuring all impacted parties are consulted and the proposer’s responses are transparent and traceable.

Core Features & Use Cases

  • Collect input from all identified impacted parties and track status (Integrated, Partially integrated, Not integrated).
  • Document each piece of advice with author, role, ETHOS, date, and the proposer’s response.
  • Generate a complete advice log at assets/advice-log-template.yaml, including non-respondent entries and modification narratives.

Quick Start

Feed the proposal details, impacted parties, and urgency into the system to activate the Advice phase and generate the full advice log in assets/advice-log-template.yaml.

Frequently Asked Questions about act-advice-phase

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

FAQPage Schema
How do I automate stakeholder advice logging for a governance proposal?

Automating stakeholder advice logging involves structuring input collection, tracking response statuses, and generating a transparent advice log. This skill coordinates those steps to capture impacted parties' input and the proposer's narrative.

What is the best way to track non-responses in a stakeholder consent workflow?

Tracking non-responses in a stakeholder consent workflow requires documenting missing entries alongside integrated and partially integrated advice. The system generates an advice log template that explicitly records non-respondents and modification narratives.

How do I structure an advice log for cross-ETHOS contexts?

Structuring an advice log for cross-ETHOS contexts requires documenting each entry with author, role, ETHOS, and date. The process outputs a complete YAML advice log capturing all impacted parties and the proposer's response narrative.

Can I use an automated advice phase for time-bound emergency proposals?

Yes, the automated advice phase applies to time-bound emergency situations and cross-ETHOS contexts. Feeding proposal details, impacted parties, and urgency into the system activates the advice phase and generates the complete log.

Does the stakeholder advice log track integration status for each entry?

Yes, the stakeholder advice log tracks integration status for each entry, categorizing input as Integrated, Partially integrated, or Not integrated. This ensures the proposer's responses to all impacted parties are transparent and traceable.