software-architect

Produce BORO-grounded solution architectures with BIE data identity specifications.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/OntoLedgy/ol_ai_context_library --skill software-architect-ontoledgy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: software-architect
Source: https://github.com/OntoLedgy/ol_ai_context_library/tree/main/skills/software-architect
Command: npx skills add https://github.com/OntoLedgy/ol_ai_context_library --skill software-architect-ontoledgy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the risk of inconsistent, unvalidated solution architectures that misalign domain requirements, data identity, and implementation by enforcing grounding in two independent ontological frameworks (BORO for world-domain analysis, BIE for deterministic data identity) and clean architecture principles.

Core Features & Use Cases

  • Three Operational Modes: High-Level Solution Design (new systems from scratch, produces BORO-grounded domain models, project foundations, and phased development plans), Feature Design (individual feature specs from approved plans), and Review Mode (gap analysis of existing solutions against design philosophy with severity-rated recommendations).
  • Approval-Gated Workflow: Ensures no design proceeds past domain model, foundations, plan, or feature spec stages without explicit user approval, preventing misalignment with business requirements.
  • Platform-Adaptable: Works with any technology stack by substituting equivalent libraries for the reference bclearer-pdk, making it reusable outside the OntoLedgy ecosystem.
  • Use Case: A team building a new healthcare data platform can use High-Level Design mode to produce a BORO-classified domain model of patient records and appointments, a BIE-aligned data identity sketch, and a phased development plan that downstream engineers and BIE ontologists can implement without rework.

Quick Start

Use the software-architect skill in High-Level Solution Design mode to produce a BORO-grounded domain model and phased development plan for a new customer relationship management system.

Frequently Asked Questions about software-architect

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

FAQPage Schema
How do I create a solution architecture grounded in ontological design?

To create an ontological solution architecture, this Skill grounds your domain requirements in the BORO world ontology and BIE data identity ontology. It produces consistent, validated solution architectures and deterministic data identity specifications for platform-adaptable systems.

What is the best way to review an existing solution architecture against clean architecture principles?

Reviewing an existing solution architecture is best handled by the Skill's Review Mode, which performs a gap analysis against design philosophy. It delivers severity-rated recommendations to identify misalignments with clean architecture compliance and ontological rigor.

Can I generate a feature specification from an approved solution architecture plan?

Yes, you can generate individual feature specifications using the Feature Design mode. This mode operates directly from previously approved plans and domain models, ensuring downstream feature specs remain ontologically consistent and aligned with clean architecture principles.

Does the ontological architecture workflow support technology stacks outside the OntoLedgy ecosystem?

Yes, the architecture workflow is platform-adaptable and supports any technology stack. You substitute equivalent libraries for the reference bclearer-pdk, making the ontological design and clean architecture validation reusable outside the OntoLedgy ecosystem.

How do I prevent misalignment between domain models and implementation during high-level solution design?

To prevent misalignment during high-level solution design, the Skill uses an approval-gated workflow. This ensures no design proceeds past the domain model, foundations, plan, or feature spec stages without explicit user approval, validating domain requirements before implementation.

When do I need deterministic data identity specifications for a new software system?

You need deterministic data identity specifications when building new systems requiring ontological rigor, such as healthcare data platforms. The Skill applies the BIE data identity ontology to produce these specifications, preventing inconsistent data design and implementation rework.