update-functional-graph

Create or update functional graph nodes from code, documents, or Figma designs.

2|2|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/accionlabs/breezeai-claude-plugin --skill update-functional-graph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-functional-graph
Source: https://github.com/accionlabs/breezeai-claude-plugin/tree/main/skills/update-functional-graph
Command: npx skills add https://github.com/accionlabs/breezeai-claude-plugin --skill update-functional-graph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of manually mapping complex functional hierarchies from diverse sources like code, documents, and Figma designs, ensuring consistent and reusable business intent modeling without technical jargon.

Core Features & Use Cases

  • Hierarchical Node Creation: Builds or updates Personas, Outcomes, Scenarios, Steps, and Actions following strict reuse-first rules.
  • Input-Type Handling: Processes code by translating to functional language, extracts intents from documents or requirements, and analyzes Figma frames for UI flows.
  • Use Case: After reviewing a new Figma onboarding design, use this Skill to integrate it into the functional graph, identifying user personas and scenarios to trace requirements against existing code.

Quick Start

Update the functional graph by creating nodes from this Figma design URL for the user dashboard feature.

Frequently Asked Questions about update-functional-graph

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

FAQPage Schema
Can I translate raw code into functional graph nodes for user flow modeling?

Creating a functional graph from code requires translating technical code into functional language to model business intents, user flows, and system behaviors across personas, outcomes, scenarios, steps, and actions using reuse-first resolution.

What is the best way to extract user scenarios from requirements documents for outcome mapping?

Functional graph hierarchy management handles persona resolution by applying strict reuse-first rules to map outcomes and scenarios, ensuring consistent modeling of user flows and system behaviors without duplicating existing nodes.

Does functional graph node creation support reuse-first resolution for existing system behaviors?

Extracting user scenarios from requirements documents for outcome mapping involves processing the text to identify business intents, then creating or updating hierarchical nodes for personas, scenarios, and actions within the functional graph.

Why should I avoid raw technical code when updating functional graph actions?

Yes, functional graph node creation supports reuse-first resolution by checking existing system behaviors and hierarchy nodes before creating new ones, ensuring platform-agnostic human actions and detailed system descriptions are consistently modeled.

Why should I avoid raw technical code when updating functional graph actions?

Avoiding raw technical code when updating functional graph actions ensures the hierarchy remains platform-agnostic and models business intents clearly, satisfying requirements for detailed system descriptions and functional language over implementation specifics.