gsd-maritime-discuss

Automate maritime GSD discuss phase requirement clarifications with YAML frontmatter and evaluation workflows.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/marinehdk/sango-mate-vro --skill gsd-maritime-discuss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-maritime-discuss
Source: https://github.com/marinehdk/sango-mate-vro/tree/main/.claude/skills/gsd-maritime-discuss
Command: npx skills add https://github.com/marinehdk/sango-mate-vro --skill gsd-maritime-discuss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enhances the GSD discuss phase by automatically introducing a maritime-specific requirement clarification framework and providing an initial Architecture Agent evaluation to guide decisions.

Core Features & Use Cases

  • Structured domain clarifications: prompts the main Agent with essential questions about vessel type, area, data sources, and safety parameters.
  • Parallel architecture evaluation: triggers a maritime-architect Agent for initial feasibility assessments in parallel to discussions.
  • Risk annotation & decision planning: produces risk labels, open questions, and MVP scope guidance to steer development.
  • Assumption mode support: when configured, identifies and records technical, safety, and performance assumptions with mitigation plans.

Quick Start

Run the maritime GSD discuss workflow to trigger phase D1 clarifications and capture Phase D2-D4 outputs.

Frequently Asked Questions about gsd-maritime-discuss

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

FAQPage Schema
How do I structure maritime requirement clarifications for early-stage project discussions?

Maritime requirement clarifications are structured using a YAML frontmatter requirement and an evaluation workflow that gathers domain inputs like vessel type, area, data sources, and safety parameters to guide decisions.

How does parallel architecture assessment work during maritime requirement discussions?

Parallel architecture assessment triggers a maritime-architect Agent alongside main discussions to deliver initial feasibility evaluations, capturing domain clarifications and recording risks or open questions simultaneously.

Can I use assumption mode to handle missing safety and performance parameters in maritime architecture evaluations?

Assumption mode identifies and records technical, safety, and performance assumptions with mitigation plans, supporting maritime architecture evaluations when explicit parameters are missing.

What is the best way to document MVP scope and risk labels for maritime GSD discussions?

The best way to document MVP scope is through an automated risk annotation workflow that produces risk labels, open questions, and MVP scope guidance to steer maritime development planning.

Do I need a specific directory structure to support on-demand resources in maritime requirement workflows?

You need the SKILL.md file with YAML frontmatter containing name and description, and you can optionally add scripts/, references/, and assets/ directories to support on-demand resources.