defining-system-context

Orchestrate the four-stage workflow to create and maintain a system-context map.

Updated Aug 18, 2025
One-click install
npx skills add https://github.com/masa-codehub/gemini_agent --skill defining-system-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: defining-system-context
Source: https://github.com/masa-codehub/gemini_agent/tree/main/.gemini/skills/defining-system-context
Command: npx skills add https://github.com/masa-codehub/gemini_agent --skill defining-system-context

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Orchestrates the creation and maintenance of the system-context (SSOT) map to align design intent with the codebase reality and produce a verified system-context.md.

Core Features & Use Cases

  • Orchestrates the four-stage workflow (Preparation, Scoping, Execution, Release) to define and keep the system context up to date.
  • Provides guidance and references for DDD modeling to clearly define system boundaries and context maps.
  • Ensures traceable, design-brief-driven documentation that reflects consensus between architecture and implementation.

Quick Start

Initiate the process by creating a Design Brief and guiding the four-step workflow to update docs/system-context.md.

Frequently Asked Questions about defining-system-context

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

FAQPage Schema
How do I define system context and maintain a single source of truth for architecture?

To define system context and maintain a single source of truth, orchestrate a four-stage workflow encompassing Preparation, Scoping, Execution, and Release to generate and update a verified system-context.md file.

What is the best way to create DDD-guided boundary definitions and context maps?

Creating DDD-guided boundary definitions and context maps requires applying domain-driven design modeling references to clearly establish system boundaries and produce design-brief-driven documentation reflecting architecture consensus.

How does design-brief-driven documentation align design intent with codebase reality?

Design-brief-driven documentation aligns design intent with codebase reality by orchestrating scoping and execution workflows that verify system context, ensuring architecture and implementation maintain traceable consensus.

Can I use this system-context workflow for architecture governance and auditing tasks?

Yes, you can use the system-context workflow for architecture governance and auditing tasks, as it explicitly supports scoping, drafting, and auditing workflows for comprehensive system-context definition and maintenance.

What are the limitations of using a single system-context map for complex architecture documentation?

The system-context map requires continuous maintenance through the four-stage workflow to avoid limitations, ensuring the single source of truth does not diverge from actual codebase reality during complex architecture evolution.