project-context-generator

Creates or updates project.md from Design Docs or Intake Briefs in English.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/Avila-Tek/avila-tek-skill-pack --skill project-context-generator-avila-tek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-context-generator
Source: https://github.com/Avila-Tek/avila-tek-skill-pack/tree/main/skills/planning-0-project-context-generator
Command: npx skills add https://github.com/Avila-Tek/avila-tek-skill-pack --skill project-context-generator-avila-tek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate or update the Project Master Context document (project_context.md) from a Design Doc or Intake Brief. Use whenever the user wants to create, update, or iterate a project context or master context. Triggers: "create the project context", "generate project_context.md", "build the master context", "bootstrap the project", "update the project context", "process this design doc", "process this intake brief". Also trigger when the user uploads a Design Doc PDF or Intake Brief docx and asks to extract or structure the project context.

Core Features & Use Cases

  • Create mode: Generate a new project_context.md from a Design Doc or Intake Brief
  • Update mode: Iterate an existing project_context.md with new information, corrections, or refinements
  • Language handling: Accept Design Doc/Intake Brief in Spanish or English; final output must be English
  • Workflow guidance: Translate terminology carefully and preserve glossary terms; append change logs on updates

Quick Start

Provide a Design Doc or Intake Brief and request to generate the project_context.md to create a new context, or provide an updated document and ask to update the project_context.md to iterate an existing one.

Frequently Asked Questions about project-context-generator

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

FAQPage Schema
How do I generate a project_context.md file from a Design Doc?

To generate a project_context.md file, provide your Design Doc or Intake Brief and request context creation. The system extracts structured sections, glossary terms, and open questions to produce a canonical Project Master Context document in formal English.

What is a Project Master Context and when do I need one?

A Project Master Context is a canonical document that consolidates design decisions and terminology to support consistent project governance. You need one when initializing a project from an Intake Brief or Design Doc to ensure all downstream decisions align with a single structured reference.

Can I update an existing project context with new information from an Intake Brief?

Yes, you can update an existing project context by providing an updated Intake Brief or Design Doc. The update mode iterates the existing project_context.md, appending change logs and preserving glossary stability while integrating the new refinements.

Does the project context generator support Design Docs written in Spanish?

Yes, the project context generator accepts Design Docs and Intake Briefs written in either Spanish or English. It carefully translates terminology during processing, but the final project_context.md output is always generated in formal English.

How does project context generation handle open questions from an Intake Brief?

Project context generation explicitly extracts and structures open questions from the Intake Brief into a dedicated section. This ensures unresolved governance issues are tracked visibly within the project_context.md rather than being buried in design documentation.

What is the best way to maintain glossary stability when updating project_context.md?

To maintain glossary stability during updates, the system preserves existing defined terms and only appends new terminology from the updated Design Doc. It logs all glossary modifications in the change log to ensure project governance consistency.