manage-context

Étoiles8

Forks0

Mis à jour17 avril 2026 à 14:39

Repair and maintain `.project/context/` so it reflects current project reality. Use when context files are stale, contradictory, still template-like, after major scope or architecture changes, before handoff, or when execution friction suggests context debt.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

MajesteitBart

MajesteitBart/delano

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

5 fichiers

SKILL.md

readonly

name	manage-context
description	Repair and maintain `.project/context/` so it reflects current project reality. Use when context files are stale, contradictory, still template-like, after major scope or architecture changes, before handoff, or when execution friction suggests context debt.

manage-context

Trigger context

.project/context/ still contains starter or placeholder language
implementation reality has drifted from spec, plan, or workstreams
repeated confusion appears around scope, terminology, ownership, architecture, or testing
a handoff, restart, or milestone review needs trustworthy context
a major scope, workflow, or architecture change landed and context was not refreshed

Required inputs

current .project/context/ files
related project docs (spec.md, plan.md, workstreams/*.md, decisions.md, progress notes)
recent execution evidence (task state, code changes, review feedback, logs)

Output schema

updated .project/context/*.md files where needed
context debt summary
explicit contradictions or evidence gaps list
recommended follow-up actions when context cannot be repaired safely

Quality checks

no obvious template placeholders remain
context matches current implementation and delivery reality
terminology is consistent across files
scope, constraints, and non-goals are explicit
progress reflects evidence, not aspiration
unresolved uncertainty is stated plainly instead of being hidden

Failure behavior

do not invent missing facts
stop short of rewriting uncertain sections as if they were confirmed
return evidence gaps and contradiction notes when repair is partial
prefer an explicit partial refresh over fake completeness

Allowed side effects

update files under .project/context/
remove stale placeholder text from context files
normalize duplicated or conflicting phrasing across context files
add concise dated notes when they improve handoff clarity

Script hooks

bash .agents/scripts/pm/validate.sh
bash .agents/scripts/pm/status.sh
bash .agents/scripts/pm/search.sh "<term>"

Execution assets

references/runbook.md
references/context-audit-checklist.md
templates/context-debt-report.md
templates/context-refresh-summary.md

Plus depuis ce dépôt

même dépôt

discovery-skill

MajesteitBart/delano

Define and approve a measurable outcome and Spec. Use when a new delivery request has unclear scope, missing outcome, or missing owner.

2026-07-248

execution-skill

MajesteitBart/delano

Execute mapped tasks with stream discipline, dependency safety checks, and evidence updates. Use when tasks are ready for implementation.

2026-07-218

ai-sdk

MajesteitBart/delano

Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".

2026-07-078

shadcn

MajesteitBart/delano

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".

2026-07-078

breakdown-skill

MajesteitBart/delano

Decompose an approved plan into atomic tasks with dependencies and acceptance criteria. Use when planning is complete and execution must be prepared.

2026-07-068

quality-skill

MajesteitBart/delano

Verify release readiness and enforce quality gates with risk-based checks and evidence capture. Use before closure or merge.

2026-07-068

name	manage-context
description	Repair and maintain `.project/context/` so it reflects current project reality. Use when context files are stale, contradictory, still template-like, after major scope or architecture changes, before handoff, or when execution friction suggests context debt.

manage-context

Trigger context

.project/context/ still contains starter or placeholder language
implementation reality has drifted from spec, plan, or workstreams
repeated confusion appears around scope, terminology, ownership, architecture, or testing
a handoff, restart, or milestone review needs trustworthy context
a major scope, workflow, or architecture change landed and context was not refreshed

Required inputs

current .project/context/ files
related project docs (spec.md, plan.md, workstreams/*.md, decisions.md, progress notes)
recent execution evidence (task state, code changes, review feedback, logs)

Output schema

updated .project/context/*.md files where needed
context debt summary
explicit contradictions or evidence gaps list
recommended follow-up actions when context cannot be repaired safely

Quality checks

no obvious template placeholders remain
context matches current implementation and delivery reality
terminology is consistent across files
scope, constraints, and non-goals are explicit
progress reflects evidence, not aspiration
unresolved uncertainty is stated plainly instead of being hidden

Failure behavior

do not invent missing facts
stop short of rewriting uncertain sections as if they were confirmed
return evidence gaps and contradiction notes when repair is partial
prefer an explicit partial refresh over fake completeness

Allowed side effects

update files under .project/context/
remove stale placeholder text from context files
normalize duplicated or conflicting phrasing across context files
add concise dated notes when they improve handoff clarity

Script hooks

bash .agents/scripts/pm/validate.sh
bash .agents/scripts/pm/status.sh
bash .agents/scripts/pm/search.sh "<term>"

Execution assets

references/runbook.md
references/context-audit-checklist.md
templates/context-debt-report.md
templates/context-refresh-summary.md