skills.rest
a3lem
a3lemCOMMUNITY
Explore all skills by this author →
GitHub

project-knowledge

Route project knowledge to appropriate stores by taxonomy and contract strength.

Updated Dec 19, 2025
Search Tags:#documentation#knowledge management#project organization#information architecture#decision log#specs
One-click install
npx skills add https://github.com/a3lem/my-claude-plugins --skill project-knowledge-a3lem
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-knowledge
Source: https://github.com/a3lem/my-claude-plugins/tree/main/plugins/project-knowledge/skills/project-knowledge
Command: npx skills add https://github.com/a3lem/my-claude-plugins --skill project-knowledge-a3lem

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a clear taxonomy and routing system for project knowledge, ensuring information is stored in the most appropriate place and can be easily retrieved. It addresses the common problem of scattered or misplaced project documentation.

Core Features & Use Cases

  • Knowledge Taxonomy: Defines distinct stores for specs, docs, decisions, notes, and journal entries, each with a specific contract strength and purpose.
  • Routing Guidance: Offers clear tables to guide users on where to store new information and where to look for existing knowledge.
  • Promotion Path: Outlines how knowledge can evolve and move between different stores based on its durability and importance.
  • Use Case: When you're unsure whether to add a new piece of information to the docs/ directory, notes/ or a Gherkin scenario in specs/, this Skill will tell you the best place to put it based on its nature.

Quick Start

Use the project-knowledge skill to determine where to store a new behavioral requirement with testable scenarios.

Frequently Asked Questions about project-knowledge

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

FAQPage Schema
How do I organize project documentation and decide where to store new information?▼

To organize project documentation effectively, use a structured taxonomy that routes information to distinct stores like specs, docs, decisions, notes, and journal entries based on contract strength and purpose.

What is the best way to manage a decision log versus project notes?▼

Managing a decision log versus project notes requires a routing system that separates durable decisions from informal notes, assigning each a specific storage location to ensure clear information architecture and easy retrieval.

When should I put a behavioral requirement in specs instead of the docs directory?▼

You should put a behavioral requirement in specs instead of the docs directory when the information has testable scenarios and requires a stronger contract, reserving docs for general project documentation.

How does knowledge promotion work across different project management stores?▼

Knowledge promotion works by moving information between stores based on its durability and importance, allowing informal notes to evolve into formal specs or permanent documentation as project requirements solidify.

Related Skills

Explore More Product & Management Skills→
knowz-ioknowz-io
1

knowz-setup

Configure the Knowz MCP server and manage vault routing files.

Official
Intermediate
fgarofalo56fgarofalo56
6

obsidian

Develop custom Obsidian plugins, templates, and automation workflows.

Community
Advanced
lengo0951lengo0951

ck:kanban

Manage task boards for project tracking and team collaboration.

Community
Intermediate
yut0takagiyut0takagi

リサーチ2スライド

Collect web topic information into a knowledge base and generate LT-ready slides.

Community
Advanced