product-context-docs

Create or update product context documentation in /docs folders.

6|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/GeneralJerel/chalk-skills --skill product-context-docs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-context-docs
Source: https://github.com/GeneralJerel/chalk-skills/tree/main/skills/product-context-docs
Command: npx skills add https://github.com/GeneralJerel/chalk-skills --skill product-context-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill helps teams create and maintain in-repo product context documentation under the /docs directory, ensuring product profiles, architecture, and tech context stay aligned with the codebase.

Core Features & Use Cases

  • Create or update the default product context documentation set at /docs/product and /docs/tech, including product-profile, product-features, sitemap, architecture, and tech-stack.
  • Reuse existing content where correct, cross-link related sections, and surface placeholders for missing details to guide future updates.
  • Bootstrap or refresh context docs for a repo when starting a new project or updating a stale documentation surface.

Quick Start

Use the product-context-docs skill to generate or refresh the /docs structure for the current repository.

Frequently Asked Questions about product-context-docs

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

FAQPage Schema
How do I create in-repo product context documentation for a new project?▼

You can generate in-repo product context documentation by bootstrapping a structured doc set under the /docs directory. It creates product-profile, product-features, sitemap, architecture, and tech-stack templates to establish a baseline documentation surface.

What is the best way to update stale architecture and tech stack docs in my repository?▼

Refreshing the existing /docs structure updates stale architecture and tech stack docs. This process reuses valid existing content, cross-links related sections, and surfaces placeholders for missing details to guide future updates.

Does generating product context docs overwrite my existing repository documentation?▼

Generating product context docs preserves existing repository documentation. The process ensures /docs folders exist and retains current content while applying default templates and linking product context to architecture and tech context.

What sections should be included in structured product documentation for a codebase?▼

Structured product documentation for a codebase should include a product profile, product features, sitemap, architecture, and tech stack. These sections ensure product context stays aligned with the codebase inside the repository.

Can I use templates to bootstrap documentation for my product's architecture and features?▼

You can use templates to bootstrap documentation for your product's architecture and features. It implements a default doc set using assets/templates to establish a structured product profile and tech context within the repository.