design/init-context

Create bounded context skeletons with standard subdirectories and README under runtime/contexts.

Updated Jan 11, 2026
One-click install
npx skills add https://github.com/venikman/fpf-foundry --skill design-init-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design/init-context
Source: https://github.com/venikman/fpf-foundry/tree/main/design/skills/design/init-context
Command: npx skills add https://github.com/venikman/fpf-foundry --skill design-init-context

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires telemetry/log-work, and includes scripts (resource) components.

What problem does it solve?

This Skill ensures a bounded context skeleton exists under runtime/contexts/<context>, preventing directory drift and enabling consistent telemetry and structure across projects.

Core Features & Use Cases

  • Create runtime/contexts/<context> with standard subdirectories: design/names, planning/workplans, telemetry/work.
  • Write runtime/contexts/<context>/README.md (if missing) without overwriting existing content.
  • Log a U.Work entry via telemetry/log-work to capture initialization actions for auditability.
  • Use when starting a new bounded context for tooling, design, or analytics pipelines to ensure consistent scaffolding.

Quick Start

Use the Init Context skill to create a Tooling context with a basic README. Example: bun develop/skills/src/design/init-context/index.ts --context Tooling --description "Tools and generators for FPF Foundry."

Frequently Asked Questions about design/init-context

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

FAQPage Schema
How do I initialize a bounded context skeleton to prevent directory drift?

You initialize a bounded context by generating a standard directory skeleton under runtime/contexts/<context> with predefined subdirectories for design, planning, and telemetry, which prevents directory drift.

What does scaffolding a bounded context do for analytics pipelines?

Scaffolding a bounded context for analytics pipelines creates consistent runtime structures and emits a telemetry U.Work record, ensuring auditability and standardized directory layout across projects.

Can I create a bounded context README without overwriting existing content?

Yes, you can create a bounded context README without overwriting existing content. The tool writes a non-destructive README.md file only if one is missing in the target runtime directory.

How do I log a U.Work entry when creating new runtime structures?

To log a U.Work entry when creating new runtime structures, the tool automatically attempts to emit a U.Work record through the telemetry/log-work dependency upon successful context initialization.

Does initializing a new context require telemetry/log-work to be set up?

While initializing a context attempts to emit a U.Work record via telemetry/log-work for auditability, the core scaffolding of directories and the non-destructive README still proceed to ensure consistent structure.