skill-architecting-pipelines-pro

Architects and audits governable agentic pipelines with node graphs, session gates, and validators.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/Noetfield-Systems/SourceA --skill skill-architecting-pipelines-pro-noetfield-systems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-architecting-pipelines-pro
Source: https://github.com/Noetfield-Systems/SourceA/tree/main/.cursor/skills/skill-architecting-pipelines-pro
Command: npx skills add https://github.com/Noetfield-Systems/SourceA --skill skill-architecting-pipelines-pro-noetfield-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing and upgrading multi-pipeline agentic systems without drift, orphaned scripts, or unverified changes is hard; this Skill enforces a governed architecture process with proof requirements for every change. ## Core Features & Use Cases - Four-pipeline architecture: Defines Truth, Safety, Presentation, and Commerce pipelines mapped to node clusters with dual navigation between pipelines and the node mesh. - Session gate ordering and change classification: Prescribes the exact session gate wire order and G0–G3 change classes, each with minimum proof requirements such as validator PASS lines and graph rows. - Drift and anti-pattern auditing: Provides a 12-point architecting checklist, proof commands, and a refusal list covering chat-only fixes, orphan pipeline scripts, and stale LOCKED docs. - Use Case: When upgrading a node skill or wiring a new validator, load this Skill to register the graph node, run the W10 validators, bump LOCKED doc versions, and sync project and personal mirror skills before claiming DONE. ## Quick Start Ask the agent to architect a new pipeline validator for the SourceA system and run the full proof checklist before marking the work done.

Frequently Asked Questions about skill-architecting-pipelines-pro

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

FAQPage Schema
How do I design a governable agentic pipeline system?

Define pipelines by outcome (Truth, Safety, Presentation, Commerce), map each to a node cluster, and require ship proof such as validator scripts for every pipeline. Use a session gate wire order so each run passes anti-staleness, safety, and zero-drift checks before execution.

How do I audit an agentic system for documentation drift?

Run the architecting checklist: quote live disk state, verify session gate receipts, confirm graph nodes exist for new capabilities, and bump LOCKED doc versions so no stale pending or missing claims remain. Refuse chat-only fixes that lack a receipt or validator PASS line.

What is a G0 to G3 change classification for pipelines?

G0-G3 classifies change scope and required proof: G0 is explain-only needing a quoted disk line, G1 is one validator or node needing a single PASS, G2 is a pipeline segment needing graph runner proof, and G3 covers session gate or skill upgrades needing the full checklist.

When should pipeline scripts be registered in a node graph?

Every pipeline script must have a corresponding row in the node graph before it ships. Orphan pipeline scripts without graph nodes are classified as architecture failures because they break the dual navigation between pipelines and the node mesh.

What are common anti-patterns in agentic pipeline architecture?

Common anti-patterns include claiming fixes without receipts or validators, bulk-editing locked documents without explicit permission, auto-running restricted pipelines, renaming locked titles with status words, and shipping pipelines without node cluster mappings.