# Docs Baseline Loading

> Docs Baseline Loading is an Agent Skill for documents published in the J-Pster/Psters_AI_Workflow repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Load and enforce mandatory project documentation baseline before implementation work.

- Skill name: `docs-baseline-loading`
- Category: [Documents](https://www.openparable.com/skill/documents/1)
- Source: https://github.com/J-Pster/Psters_AI_Workflow/blob/HEAD/plugins/psters-ai-workflow/skills/docs-baseline-loading/SKILL.md
- Repository: J-Pster/Psters_AI_Workflow (291 GitHub stars when collected)

## SKILL.md

# Docs Baseline Loading

Use this skill before implementation commands to guarantee the project docs baseline is present, readable, and aligned.

## Trigger conditions

- Running `/pwf-work`, `/pwf-work-plan`, `/pwf-work-light`, or `/pwf-work-tdd`.
- Starting implementation in a project with missing or stale docs.

## Mandatory baseline docs

- `docs/infrastructure.md`
- `docs/architecture.md`
- `docs/integrations.md`
- `docs/environments.md`
- `docs/glossary.md`

Read these before coding.

## Optional but high-value context docs

- `docs/solutions/patterns/critical-patterns.md` (if exists)
- `docs/modules/<module>.md` when backend module scope is touched
- `docs/features/<feature>.md` when frontend feature scope is touched
- `docs/lambdas/<repo>.md` when Lambda scope is touched
- `docs/runbooks/README.md` when operational/deploy behavior is touched

## If baseline docs are missing

Create missing files immediately before implementation.

### Required minimum sections

`docs/infrastructure.md`:
- `Infrastructure Overview`
- `Environments`
- `Core Services and Dependencies`
- `Deployment and Operations`
- `Known Constraints and Risks`

`docs/architecture.md`:
- `System Overview`
- `Technology Stack`
- `Module and Service Boundaries`
- `Data and Request Flows`
- `Architecture Invariants`

`docs/integrations.md`:
- `Integration Catalog`
- `Authentication and Access`
- `Contracts and Data Flows`
- `Failure Modes and Retries`
- `Ownership`

`docs/environments.md`:
- `Environment Matrix`
- `Configuration and Secrets Boundaries`
- `Deployment Differences`
- `Operational Access`

`docs/glossary.md`:
- `Domain Terms`
- `Technical Terms and Acronyms`
- `Naming Conventions`

## Constraints

- Do not create duplicate variants of baseline docs.
- Update canonical docs in place.
- Keep docs project-specific and operational (no filler).

---

Source: https://www.openparable.com/skill/documents/docs-baseline-loading (OpenParable). Cite the canonical URL above.