product-context-docs

Create and update in-repo product context docs under /docs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Creating and maintaining in-repo product context documentation under /docs is error-prone and time-consuming when teams duplicate work or lose alignment between product profiles, features, sitemap, architecture, and tech stack.

Core Features & Use Cases

  • Bootstrap the default /docs structure (product-profile, product-features, sitemap, architecture, tech-stack) for a new repo.
  • Update existing product context content to reflect changes in the codebase or strategy.
  • Cross-link product docs to improve navigation and ensure consistency across architecture and tech decisions.

Quick Start

Create or refresh the /docs product context docs 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 bootstrap product context documentation in a new repository?

Product context documentation captures a repository's profile, features, sitemap, architecture, and tech stack. It lives under the /docs directory and uses YAML frontmatter templates to maintain consistent in-repo product context.

How do I update outdated architecture and tech stack docs in my repo?

You can refresh outdated product context docs by applying predefined YAML frontmatter templates to your existing /docs files. This updates architecture, tech stack, and features to reflect current codebase changes and product strategy.

What's the best way to structure in-repo documentation for product context?

The best way to structure in-repo product context documentation is using a predefined /docs directory layout. This organizes product profile, features, sitemap, architecture, and tech stack files with standardized YAML frontmatter templates.

Can I cross-link product features and architecture docs within my repository?

Yes, you can cross-link product features and architecture docs within your repository. The skill improves navigation by ensuring consistency and cross-linking between architecture and tech decisions across the /docs structure.

Do I need YAML frontmatter to maintain product context docs?

Yes, YAML frontmatter is required to maintain product context docs. The skill uses YAML frontmatter templates to generate and update a standard doc set under the /docs repository structure consistently.

When should I refresh my repository's product profile and sitemap documentation?

You should refresh your repository's product profile and sitemap documentation when the codebase or product strategy changes. Updating outdated /docs content ensures alignment between current features and documented architecture.