skills.rest
productengineered
productengineeredCOMMUNITY
Explore all skills by this author →
GitHub

agent-shared-context

Load shared terminology, review-cycle guidance, and task-state protocols into agent prompts.

Updated Apr 9, 2026
Search Tags:#workflow#prompts#terminology#task-state#review-cycle#agent-context
One-click install
npx skills add https://github.com/productengineered/parsely --skill agent-shared-context-productengineered
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-shared-context
Source: https://github.com/productengineered/parsely/tree/main/.claude/skills/workflow/agent-shared-context
Command: npx skills add https://github.com/productengineered/parsely --skill agent-shared-context-productengineered

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shared terminology, review cycle overview, and task state protocol references are preloaded into the agent context to avoid duplication across prompts and ensure consistency.

Core Features & Use Cases

  • Terminology glossary and standardized definitions for Claude Tasks, Epic, Story, Task, Bug, and TechDebt.
  • Review Cycle guidelines and Task State Protocol references to coordinate multi-agent workflows and ensure consistent state management across tasks and stories.
  • Schema versioning guidance and loading strategies to propagate context across prompts and maintain alignment across agents.

Quick Start

Load the shared agent context into all agent prompts to ensure consistent terminology and task-state handling across prompts.

Frequently Asked Questions about agent-shared-context

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

FAQPage Schema
How do I standardize terminology across multiple AI agents to avoid inconsistent prompts?▼

Avoid duplicating context in multi-agent workflows by loading a shared schema at activation that propagates unified terminology and task-state references across all agent prompts automatically.

What is a shared agent context and how does it unify multi-agent workflows?▼

Schema versioning ensures continued alignment across agents by providing loading strategies that maintain consistent terminology and task-state protocol references even as the shared context evolves.

How do I implement a task-state protocol for coordinating review cycles between agents?▼

Load shared context into all agent prompts at activation to ensure consistent terminology and task-state handling across multi-agent workflows without duplicating definitions in individual prompts.

Can I use a single shared context for Claude Tasks, Epics, and Stories across different agents?▼

The shared agent context applies to multi-agent workflows relying on common terminology and task-state protocols, making it suitable for coordinating tasks and stories across multiple agents.

Do I need to manually copy terminology definitions into every agent prompt?▼

Loading the shared context at activation automatically propagates standardized terminology and task-state protocols across prompts, eliminating the need to manually duplicate definitions in each agent.

Related Skills

Explore More Software Engineering Skills→
sambeausambeau
5

kanbanzai-getting-started

Orient an agent to repository context and Kanbanzai workflow conventions at session start.

Community
Intermediate
orakitineorakitine

Task Workflow Manager

Automate task lifecycle management across define, refine, implement, and review stages.

Community
Advanced
yangjizhou99yangjizhou99

Company Manager Skill

Coordinates multi-project AI agent tasks via role separation and file-based tracking.

Community
Advanced
kevinnftkevinnft
13

ubiquitous-language

Extract domain terminology from conversations into a structured glossary file.

Community
Intermediate