Doe Sem

Community

jgsystemsconsulting

doe-sem

Knowledge base from DOE Systems Engineering Methodology (SEM) Version 3 — the DOE SDLC for IT investments. Use for staged systems lifecycle planning through maintenance, Stage Exits, Structured Walkthroughs, In-Stage Assessments, requirements traceability, and CMM-aligned process discipline. Covers SEM3 (2002) guidance only; does not replace modern DevSecOps tooling standards, DOE O 413.3B capital-asset directives, or current CIO policy supersessions.

Overview

Publisher	jgsystemsconsulting
Repository	`jgs-se-knowledge-packs`
Skill name	`doe-sem`
Stars	121
Forks	1
Bundled files	11
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
11 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by jgsystemsconsulting on GitHub. Read the source before you install it.

Installation

Install the Doe Sem AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/jgsystemsconsulting/jgs-se-knowledge-packs/tree/main/packs/doe-sem
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/jgsystemsconsulting/jgs-se-knowledge-packs.git /tmp/jgs-se-knowledge-packs
mkdir -p .claude/skills
cp -r /tmp/jgs-se-knowledge-packs/packs/doe-sem .claude/skills/doe-sem

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Doe Sem in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Doe Sem on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Doe Sem is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

DOE Systems Engineering Methodology (SEM) Version 3

Source: DOE SEM3 / DOE G 200.1-1A (US Government work, public domain) | Chapters: 7

When to use

Reach for this pack when planning or assessing a DOE-style systems development lifecycle for IT investments — especially stage gates (Stage Exits), peer Structured Walkthroughs, independent In-Stage Assessments, planning/QA/CM plan triad, requirements traceability, construction vs design boundaries, acceptance, or the nested maintenance process model.

Prerequisites: none — plain Markdown; no MCP server, API key, or licence tier needed at runtime.

How to Use This Skill

Without arguments — load the core frameworks below.
With a topic — ask about lifecycle stages, Stage Exit, walkthroughs, planning, requirements, design, construction, test/acceptance, or maintenance.
With a chapter — ask for ch01 through ch07.

Supporting files: glossary.md, patterns.md, cheatsheet.md.

Core Frameworks & Mental Models

What SEM is

DOE’s Systems Development Lifecycle guidance for IT investments (Office of the CIO). Version 3 renames software-centric SEM to systems engineering for IT projects and aligns practices with SEI CMM-SW Level 2/3 process areas.

Eight lifecycle stages

Planning
Requirements Definition
Functional Design
System Design
Construction (formerly Programming)
Integration and Testing
Installation and Acceptance
Maintenance (nested change lifecycle)

Quality machinery (every development stage)

Mechanism	Role
Structured Walkthrough	Peer technical review of work products
In-Stage Assessment	Independent QA review of stage deliverables
Stage Exit	Owner/stakeholder go / continue / abandon decision

Planning triad

Project Plan + Quality Assurance Plan + Configuration Management Plan baseline how the project will be managed, assured, and controlled.

Traceability

Requirements Traceability Matrix links needs → requirements → design → test → acceptance evidence.

Modern use note

Source date is September 2002. Keep stage intents, gates, and CM/QA discipline; modernize tools (cloud, CI/CD, agile increments) without dropping exits and baselining.

Chapter Index

#	Section	Key content
ch01	Purpose and Context	SEM scope, v3 changes, CMM alignment, DOE CIO context
ch02	Lifecycle Model & Quality Reviews	Eight stages; walkthroughs; assessments; Stage Exits; tailoring
ch03	Planning Stage	Feasibility, plans triad, risk, EA, performance measures
ch04	Requirements & Functional Design	RTM, baselines, logical design
ch05	System Design & Construction	Physical design, build, unit verification, CM
ch06	Integration Test & Acceptance	System test, install, owner acceptance, training
ch07	Maintenance	Nested change process model and metrics

Topic Index

Acceptance / owner decision → ch06
CMM-SW alignment → ch01, ch02
Configuration management plan → ch03, ch05, ch07
Construction stage → ch05
COTS considerations → ch05, ch07
Enterprise Architecture (DOE EA) → ch03
Feasibility analysis → ch03
Functional design → ch04
In-Stage Assessment → ch02
Installation → ch06
Integration and testing → ch06
Lifecycle stages overview → ch02
Maintenance process model → ch07
Performance measures → ch03, ch06
Planning stage → ch03
Project plan → ch03
Quality assurance plan → ch03
Requirements definition → ch04
Requirements traceability matrix (RTM) → ch04, ch06
Risk management → ch03
Stage Exit → ch02, ch06
Structured Walkthrough → ch02
System design → ch05
System owner / users → ch03, ch06
Tailoring by project size → ch02, ch07

Supporting Files

glossary.md — SEM lifecycle terms with chapter references
patterns.md — implementation patterns (When/How/Trade-offs)
cheatsheet.md — decision rules, stage map, tells & smells

Scope & Limits

This pack covers DOE Systems Engineering Methodology Version 3 (SEM3_1231.pdf, September 2002, DOE G 200.1-1A) — the DOE SDLC for IT investments — as synthesized reference notes. Extracted page count recorded in PACK.yaml is 318. It does not cover: current superseding DOE CIO directives if any; DOE O 413.3B capital asset project management in full; agile/DevSecOps toolchains as mandates; or non-IT nuclear/facility systems engineering methods. US Government public domain work. No source-material download link is published. In-PDF third-party copyright check at build found no copyright notices (IEEE/SEI are citations only).

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Doe Sem AI skill do?

Why use Doe Sem on TypingMind?

Because you install it once and use it with any model. Doe Sem is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Doe Sem in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jgsystemsconsulting/jgs-se-knowledge-packs/tree/main/packs/doe-sem. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Doe Sem?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Doe Sem?

As many as you like. As long as a model supports skills, you can use Doe Sem with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Doe Sem AI skill free?

It is published on GitHub by jgsystemsconsulting. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Auto Qa

openclaw

OrganizationPopular

Run OpenClaw-wide autonomous QA and live/stress campaigns across independent subsystem lanes, with verified fixes and a resumable evidence report.

Autoreview

Structured code review when explicitly requested, preferring OpenAI/Codex before Claude.

Claw Score

Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.

Clawsweeper

Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

DOE Systems Engineering Methodology (SEM) Version 3

When to use

How to Use This Skill

Core Frameworks & Mental Models

What SEM is

Eight lifecycle stages

Quality machinery (every development stage)

Planning triad

Traceability

Modern use note

Chapter Index

Topic Index

Supporting Files

Scope & Limits

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now