Objectives

Generate and evaluate Solution Outline Objectives from the Requirements Inventory.

Updated Feb 1, 2026

Search Tags:#architecture #documentation #requirements #governance #traceability #inventory #objectives

Ready to run

npx skills add https://github.com/zthanos/so-workspace --skill objectives

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Objectives
Source: https://github.com/zthanos/so-workspace/tree/main/assets/templates/skills/objectives
Command: npx skills add https://github.com/zthanos/so-workspace --skill objectives

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Objectives lifecycle ensures the architectural intent is consistently derived from the validated Requirements Inventory, enabling traceable, aligned, and auditable objectives across the Solution Outline.

Core Features & Use Cases

Generate objectives from the Requirements Inventory to establish architectural intent.
Evaluate and patch the Objectives document to resolve inconsistencies while preserving inventory fidelity.
Recheck changes and answer structured questions about objectives, systems, stakeholders, scope, and constraints.

Quick Start

Generate the Solution Outline Objectives from the current Requirements Inventory and save to docs/02_objectives/objectives.md.

Frequently Asked Questions about Objectives

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

FAQPage Schema

How do I derive architectural objectives from a requirements inventory?▼

You can derive architectural objectives by generating the Solution Outline Objectives directly from the validated Requirements Inventory, capturing architectural intent while reflecting business context, scope, stakeholders, and systems.

What is the best way to maintain traceability when requirements inventory evolves?▼

To maintain traceability as inventory evolves, apply the objectives workflow to generate, evaluate, patch, and recheck the Objectives document, preserving inventory fidelity across the Solution Outline lifecycle.

How do I resolve inconsistencies in architectural objectives documentation?▼

To resolve inconsistencies in architectural objectives documentation, evaluate and patch the Objectives document to address discrepancies while strictly preserving the validated Requirements Inventory fidelity.

Can I answer structured questions about stakeholders and scope using objectives documentation?▼

Yes, you can answer structured questions about stakeholders, scope, systems, flows, and constraints by applying the recheck workflow to the generated Objectives document derived from the Requirements Inventory.

Do I need a validated Requirements Inventory before generating architectural objectives?▼

Yes, a validated Requirements Inventory is required before generating architectural objectives, serving as the foundational input to establish traceable, aligned, and auditable intent for the Solution Outline.