skills.rest
commontoolsinc
commontoolsincOFFICIAL
Explore all skills by this author →
Website𝕏@CommonToolsGitHub

knowledge-base

Resolve documentation, code, and spec conflicts using a defined source hierarchy.

37|12|Updated May 10, 2024
Search Tags:#docs#guidelines#conflict-resolution#specs#knowledge-base#source-hierarchy#runtime-code
One-click install
npx skills add https://github.com/commontoolsinc/labs --skill knowledge-base
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: knowledge-base
Source: https://github.com/commontoolsinc/labs/tree/main/.claude/skills/knowledge-base
Command: npx skills add https://github.com/commontoolsinc/labs --skill knowledge-base

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill establishes a clear source hierarchy to resolve conflicts between documentation, code, specs, and runtime behavior, ensuring consistent decision-making.

Core Features & Use Cases

  • Authoritative sourcing: Defines the priority order for sources (Specs > Working Code > Runtime Code > Plain Text Docs).
  • Conflict resolution guidance: Provides concrete rules to decide which artifact governs behavior.
  • On-demand reference: Directs users to essential docs, tests, and runtime implementations during investigation.

Quick Start

Load this skill first when investigating system behavior and consult the hierarchy rules to resolve conflicts.

Frequently Asked Questions about knowledge-base

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

FAQPage Schema
How do I resolve conflicts when documentation, code, and specs disagree?▼

Establish a clear source hierarchy to resolve conflicts: prioritize Specs over Working Code, Working Code over Runtime Code, and Runtime Code over Plain Text Docs. This ensures consistent decision-making when sources contradict each other.

What's the authoritative order for docs, specs, and code when they contradict?▼

Follow this hierarchy: Specs > Working Code > Runtime Code > Plain Text Docs. The highest-priority source in this order governs behavior when artifacts disagree.

When should I consult specs versus actual running code to understand system behavior?▼

Consult specs first as the authoritative source. If specs are absent or unclear, use working code. Runtime code provides observed behavior only when working code is unavailable. Plain text docs are lowest priority.

How do I investigate system behavior when multiple sources provide conflicting information?▼

Apply provenance-aware decision-making using the defined hierarchy. Identify all conflicting sources, determine each source's rank in the precedence framework, and let the highest-ranking source resolve the conflict.

What framework should I use to determine which artifact is authoritative?▼

Use this precedence framework: Specs establish intent, Working Code shows implementation, Runtime Code reveals actual behavior, and Plain Text Docs provide context. Load this hierarchy first when investigating disagreements.

Related Skills

Explore More Software Engineering Skills→
VectorInstituteVectorInstitute

fix-merge-conflicts

Resolve git merge conflicts across dependency, source, and configuration files.

Official
Advanced
PostergullyPostergully

query

Query a knowledge base with 3-layer search and citation-backed answers.

Community
Advanced
boshu2boshu2
418

provenance

Trace provenance and source lineage for knowledge artifacts across sessions and citations.

Community
Advanced
CpiconCpicon
1

Agent Generation

Generate project-specific Claude Code agent teams and templates from a codebase.

Community
Advanced