skills.rest
MicrotronX
MicrotronXCOMMUNITY
Explore all skills by this author →
GitHub

mxSpec

Creates or updates specifications in mxLore knowledge DB via MCP-Tools with automatic acceptance-criteria tracking and archiving.

29|8|Updated Apr 6, 2026
Search Tags:#documentation#specification#MCP#ADR#acceptance-criteria#mxLore
One-click install
npx skills add https://github.com/MicrotronX/mxLore --skill mxspec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mxSpec
Source: https://github.com/MicrotronX/mxLore/tree/main/claude-setup/skills/mxSpec
Command: npx skills add https://github.com/MicrotronX/mxLore --skill mxspec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

mxSpec provides a concise workflow to create or update formal specifications in the mxLore knowledge database and automatically track acceptance criteria, including auto-archiving when completion criteria are met.

Core Features & Use Cases

  • Create or update specifications via MCP-Tools in the mxLore knowledge DB.
  • Track acceptance criteria with auto-archive on full completion.
  • Link related ADRs/plans and manage references to ensure traceability.

Quick Start

Create or update a specification for the current feature in mxLore using MCP-Tools.

Frequently Asked Questions about mxSpec

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

FAQPage Schema
How do I write and track acceptance criteria for feature specifications?▼

Acceptance criteria for feature specifications are tracked automatically in the mxLore knowledge DB, triggering auto-archiving when all verification steps are fulfilled. This ensures requirements remain verifiable and linked throughout implementation.

What is the best way to create formal specifications linked to ADRs and plans?▼

Creating formal specifications linked to ADRs and plans is done via MCP-Tools in the mxLore knowledge DB, managing references to ensure traceability across related architectural decisions and project plans.

When do I need to define acceptance criteria before planning and implementation?▼

Acceptance criteria must be defined before planning and implementation when you request a spec to ensure verification steps are established upfront and related items are linked via MCP tooling.

Can I use MCP-Tools to update existing requirements in a knowledge database?▼

MCP-Tools can update existing requirements in the mxLore knowledge database, applying changes to formal specifications while maintaining automatic tracking and archiving of completion criteria.

Does the specification auto-archive process work when all acceptance criteria are met?▼

The specification auto-archive process works automatically when all acceptance criteria are fully met, ensuring completed requirements are archived without manual intervention via MCP tooling.

How do I ensure traceability between specifications and related architectural decisions?▼

Traceability between specifications and related architectural decisions is ensured by linking ADRs and plans within mxLore, managing references through MCP-Tools to maintain connections across the knowledge DB.

Related Skills

Explore More Product & Management Skills→
MicrotronXMicrotronX
29

mxDecision

Create and maintain Architecture Decision Records in the mxLore knowledge DB via MCP-Tools.

Community
Advanced
ramybarsoumramybarsoum

implementation-plan

Convert technical designs into phased implementation plans with acceptance criteria.

Community
Advanced
joshbandjoshband
3

impl

Execute LocusQ DSP and WebView implementation tasks with ADR-compliant traceability.

Community
Advanced
ReadyStateChangeReadyStateChange

writing-functional-specs

Convert draft functional specifications into contract-facing specs with acceptance criteria.

Official
Advanced