skills.rest
jon23d
jon23dCOMMUNITY
Explore all skills by this author →
GitHub

system-knowledge

Access application behavior from markdown domain files for ticket writing.

3|1|Updated Mar 11, 2026
Search Tags:#scoping#documentation#knowledge base#behavior#ticket writing
One-click install
npx skills add https://github.com/jon23d/skillz --skill system-knowledge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: system-knowledge
Source: https://github.com/jon23d/skillz/tree/main/skills/system-knowledge
Command: npx skills add https://github.com/jon23d/skillz --skill system-knowledge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured way for agents to understand an application's current behavior without needing to read source code, ensuring accurate ticket writing and feature scoping.

Core Features & Use Cases

  • Behavioral Documentation: Access and understand application behavior through plain-prose domain files.
  • Ticket Pre-writing Analysis: Use existing documentation to inform ticket creation and avoid reinventing the wheel.
  • Bootstrapping Documentation: Delegate the creation of missing behavioral documentation from existing issues.
  • Use Case: Before writing a ticket to change the login flow, an agent uses this Skill to read docs/auth.md to understand the current magic link expiration and session management rules.

Quick Start

Use the system-knowledge skill to understand the current behavior of the authentication system by reading the relevant domain files.

Frequently Asked Questions about system-knowledge

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

FAQPage Schema
How do I document application behavior for accurate ticket writing?▼

You can document application behavior using markdown files organized by domain and feature, enabling agents to understand current rules without reading source code for accurate ticket writing.

What is the best way to scope new features using existing knowledge base documentation?▼

Scoping new features is best done by reading plain-prose domain files to understand current application behavior, ensuring new feature scopes align with existing system rules and logic.

Can I bootstrap missing behavioral documentation from existing issues?▼

Yes, you can bootstrap missing behavioral documentation by delegating the creation of plain-prose domain files from existing issues to build out the knowledge base.

Does application behavior documentation require a specific file structure?▼

Yes, application behavior documentation requires adherence to a specific domain file structure to maintain clarity and consistency across the knowledge base.

How do I prevent reinventing the wheel when creating tickets for system changes?▼

To prevent reinventing the wheel during ticket creation, analyze existing behavioral documentation beforehand to understand current application logic and inform your ticket writing.

Related Skills

Explore More Product & Management Skills→
whjelmarwhjelmar

memory-knowledge

Manage persistent topic-based knowledge files in markdown with an index.

Community
Intermediate
alex-tgkalex-tgk

ux-researcher-designer

Generate data-driven personas from JSON user research data and interviews.

Community
Intermediate
haryelramalhoharyelramalho

review

Compare HEAD against a fixed point and analyze code diffs.

Community
Advanced
C0ntr0lledCha0sC0ntr0lledCha0s
8

documentation-writer

Generate module READMEs, user guides, and technical references from source code.

Community
Basic