一键在 Manus 中运行任何 Skill

context-load

星标15

分支2

更新时间2026年7月22日 06:40

Load full project context at session start. Read STATE.md, PLAN.md, PROJECT.md, CONVENTIONS.md, and ARCHITECTURE.md to brief any agent on where work stands.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

DVNghiem

DVNghiem/FlowDeck

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Context Load Skill

Gets any agent up to speed in under 30 seconds. Loads the minimum set of project files needed to understand what phase the work is in and what comes next.

When to Activate

Activate at the start of every session, or when:

Starting a new OpenCode session
An agent seems unaware of the current project state
You want to brief a new agent on the project

Core Principles

Load context before asking any agent to do work
Read in dependency order: state first, then plan, then code conventions
Surface blockers immediately — don't proceed if STATE.md shows a blocker

Workflow

Read STATE.md — current phase, active plan, completed steps, blockers
Read active PLAN.md — (path from STATE.md) next tasks and success criteria
Read ~/.fd-plan//PROJECT.md — project name, stack, constraints
Read .codebase/CONVENTIONS.md — naming patterns, import style, error handling
Read .codebase/ARCHITECTURE.md — component layout and data flow

Context Files

File	Contains	Load Order
`STATE.md`	Current phase, active plan, completed steps	1st
`~/.fd-plan/<slug>/<topic>/plan.md`	Tasks, success criteria	2nd
`~/.fd-plan/<slug>/PROJECT.md`	Project context, constraints	3rd
`.codebase/CONVENTIONS.md`	Naming, imports, patterns	4th
`.codebase/ARCHITECTURE.md`	System design, components	5th

Output Format

After loading context, produce this briefing:

## Project Context Loaded

**Project**: [name from PROJECT.md]
**Phase**: [N] — [phase name]
**Status**: [discuss | plan | execute | review]
**Active Plan**: [path to PLAN.md]

**Completed Steps**: [N of M]
**Next Step**: [next incomplete step from PLAN.md]

**Blockers**: [none | description]

**Stack**: [from PROJECT.md or CONVENTIONS.md]
**Key Conventions**: [2-3 most important patterns]

If any file is missing, note it: "STATE.md not found — run /fd-task to initialize."

同仓库更多 Skills

同仓库

context-budget

DVNghiem/FlowDeck

Optimize token usage and context window discipline. Reduce costs and improve response quality through smart context management.

2026-07-2215

context-steward

DVNghiem/FlowDeck

Unified context lifecycle for FlowDeck sessions — ingest, filter, prune, protect, summarize, and persist with telemetry.

2026-07-2215

change-impact-radar

DVNghiem/FlowDeck

Predict affected files, modules, APIs, tests, and DB paths before changes. Returns an impact map for human review.

2026-07-2215

codebase-mapping

DVNghiem/FlowDeck

Map architecture, conventions, and file structure into `.codebase/`. Use when onboarding or before deep feature work.

2026-07-2215

confidence-aware-planning

DVNghiem/FlowDeck

Plan differently when the agent has low certainty — ask for clarification or narrow scope instead of pretending full understanding.

2026-07-2215

context-guard

DVNghiem/FlowDeck

Protect critical context from pruning during compaction. Preserve active plans, safety files, pending operations, and user intent anchors.

2026-07-2215

Context Load Skill

Gets any agent up to speed in under 30 seconds. Loads the minimum set of project files needed to understand what phase the work is in and what comes next.

When to Activate

Activate at the start of every session, or when:

Starting a new OpenCode session

An agent seems unaware of the current project state

You want to brief a new agent on the project

Core Principles

Load context before asking any agent to do work

Read in dependency order: state first, then plan, then code conventions

Surface blockers immediately — don't proceed if STATE.md shows a blocker

Workflow

Read STATE.md — current phase, active plan, completed steps, blockers

Read active PLAN.md — (path from STATE.md) next tasks and success criteria

Read ~/.fd-plan//PROJECT.md — project name, stack, constraints

Read .codebase/CONVENTIONS.md — naming patterns, import style, error handling

Read .codebase/ARCHITECTURE.md — component layout and data flow

Context Files

File

Contains

Load Order

STATE.md

Current phase, active plan, completed steps

1st

~/.fd-plan/<slug>/<topic>/plan.md

Tasks, success criteria

2nd

~/.fd-plan/<slug>/PROJECT.md

Project context, constraints

3rd

.codebase/CONVENTIONS.md

Naming, imports, patterns

4th

.codebase/ARCHITECTURE.md

System design, components

5th

Output Format

After loading context, produce this briefing:

## Project Context Loaded **Project**: [name from PROJECT.md] **Phase**: [N] — [phase name] **Status**: [discuss | plan | execute | review] **Active Plan**: [path to PLAN.md] **Completed Steps**: [N of M] **Next Step**: [next incomplete step from PLAN.md] **Blockers**: [none | description] **Stack**: [from PROJECT.md or CONVENTIONS.md] **Key Conventions**: [2-3 most important patterns]

If any file is missing, note it: "STATE.md not found — run /fd-task to initialize."

name	context-load
description	Load full project context at session start. Read STATE.md, PLAN.md, PROJECT.md, CONVENTIONS.md, and ARCHITECTURE.md to brief any agent on where work stands.
origin	FlowDeck