scepter

Build a CLI-driven knowledge graph of code notes with claim-level traceability.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/wayspurrchen/scepter --skill scepter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scepter
Source: https://github.com/wayspurrchen/scepter/tree/main/claude/skills/scepter
Command: npx skills add https://github.com/wayspurrchen/scepter --skill scepter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SCEpter provides a CLI-first workflow to build a persistent knowledge graph of code-related notes with claim-level traceability. It targets AI-assisted software development scenarios where agents need context, decisions, and rationale across notes, designs, tests, and code, across multiple projections. It enforces frontmatter-driven metadata, claim syntax, and cross-note referencing, requiring fully qualified claim paths, derived relationships, and scheduled verification tasks.

Core Features & Use Cases

  • CLI-first knowledge graph across notes (Decision, Requirement, Design, Tests) with cross-project traceability
  • Claim-level traceability enabling precise, cross-note mappings like {R001.§1.AC.01}
  • Lightweight governance: frontmatter-driven metadata, status tracking, and lifecycle annotations
  • Powerful discovery and querying capabilities to surface relevant context for AI agents

Quick Start

Install SCEpter in your repo, run scepter config to initialize note types, then create and link your first notes with explicit claim references.

Frequently Asked Questions about scepter

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

FAQPage Schema
How do I build a knowledge graph for AI-assisted software development notes?

Build a knowledge graph for AI-assisted development by using a CLI-first workflow that creates persistent notes with frontmatter-driven metadata, claim syntax, and cross-note referencing to provide agents with context and rationale.

What is claim-level traceability for software development notes?

Claim-level traceability is the mechanism of creating precise, cross-note mappings using fully qualified claim paths like {R001.§1.AC.01} to link decisions, requirements, designs, and tests across multiple projections.

How do I provide context to AI coding agents across multiple projects?

Provide context to AI coding agents by enforcing frontmatter-driven metadata and using powerful discovery and querying capabilities to surface relevant decisions and rationale from a persistent knowledge graph.

Can I use CLI tools to manage lifecycle annotations for software design notes?

Yes, CLI tools can manage lightweight governance for software design notes by enforcing frontmatter-driven metadata, tracking status, and applying lifecycle annotations to maintain cross-project traceability.

What's the best way to track decisions and requirements for AI coding agents?

Track decisions and requirements by establishing a persistent knowledge graph with claim-level traceability, enabling scheduled verification tasks and derived relationships to surface precise context for AI agents.

Why does my AI coding agent lack context from my software development notes?

AI coding agents lack context when software development notes do not enforce claim syntax, fully qualified claim paths, or cross-note referencing, preventing the discovery and querying capabilities from surfacing relevant rationale.