Simple Project Expert

Name: Simple Project Expert
Availability: InStock
Author: ormastes

Map Simple subprojects to SPipe/SPstack pipeline paths with verification steps.

Updated May 27, 2026

Search Tags:#developer onboarding #release verification #repository workflow #subproject mapping #SPipe pipeline #SimpleOS

Ready to run

npx skills add https://github.com/ormastes/Spipe --skill simple-project-expert

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Simple Project Expert
Source: https://github.com/ormastes/Spipe/tree/main/doc/00_llm_process/project_expert/simple
Command: npx skills add https://github.com/ormastes/Spipe --skill simple-project-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams document and consistently coordinate project-level process knowledge across Simple and its subprojects, so changes land with the right development pipeline and verification steps.

Core Features & Use Cases

Project-level process ownership: captures what the Simple repository and its subprojects should do at a process/pipeline level.
Subproject directory mapping: lists where key areas live (compiler, app tools, libraries, runtime, SimpleOS, examples) so contributors know which parts belong where.
Cross-cutting pipeline guidance: directs full-feature development to the appropriate areas and uses a verification gate before release.
Update discipline: prompts maintainers to record when a subproject gains its own SPipe module, including its directory, owner, setup, and verification commands.

Quick Start

Use this expert as the canonical reference for where each Simple subproject lives and what pipeline route to follow before release.

Frequently Asked Questions about Simple Project Expert

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

FAQPage Schema

How do I map Simple subprojects to the correct repository directories for development?▼

Subproject directory mapping lists where key areas like compiler, app tools, libraries, runtime, SimpleOS, and examples live so contributors know exactly which parts belong where in the repository.

What is the correct SPipe pipeline route for full-feature development in the Simple repository?▼

The correct SPipe pipeline route directs full-feature development to the appropriate areas and requires a verification gate using a /verify step prior to release.

How do I verify SimpleOS contributions before release?▼

To verify SimpleOS contributions before release, direct authors to /dev or /spipe plus a /verify step to ensure changes land with the correct development pipeline and verification steps.

When do I need to record a new SPipe module for a Simple subproject?▼

You need to record a new SPipe module when a subproject gains its own module, prompting maintainers to document its directory, owner, setup, and verification commands.

Does the Simple repository workflow support both compiler and app tooling contributions?▼

Yes, the Simple repository workflow applies to contributions that touch compiler, app tooling, libraries, runtime, SimpleOS, or examples, requiring the correct SPipe/SPstack pipeline path.