Knowledge Capture

Knowledge Capture

Runtime Context

Before acting, resolve ` using the runtime bootstrap rules, then read /.workflow/runtime.md and /.workflow/manifest.yml`; do not assume non-default workflow paths or default ids.

Use this skill to write approved knowledge changes and move information from local member context into durable project knowledge.

Workflow

1. Resolve the current member id using /.workflow/runtime.md.
2. If writing current-member workspace content or promoting current-member local material, read relevant sections from /members/.md and read local workspace instructions when they exist.
3. Classify the material as local context, shared member context, project knowledge, or task candidate.
4. Read /.workflow/rules/knowledge.md.
5. Read /.workflow/schemas/common.md.
6. Read the relevant target area schema under /.workflow/schemas/.
7. Store purely local material only under /workspace//local/; follow /.workflow/rules/workspace.md and /.workflow/schemas/workspace.md when maintaining personal worklists or logs.
8. Create the target directory on demand when writing a new file; do not assume empty knowledge area directories already exist.
9. Promote approved local material when the user has decided it should become team knowledge.
10. Use references/placement.md to choose the target area for durable material.
11. Use member and group templates when creating approved member profiles or group documents; confirm membership updates before writing.
12. Keep canonical-language files as the authoritative source and localized files as translations only.
13. Before writing, produce a capture dry-run with the fields defined below unless the user explicitly asked for a single-file wording or metadata edit and the target path and schema are already known.

Read /.workflow/rules/delivery.md before making task, planning, or delivery-related structural changes.

If the user has not decided whether the content belongs in knowledge, use knowledge-intake first.

Guardrails

• Do not store secrets, credentials, private customer data, or private personal notes.
• Do not treat member workspace notes as project facts until promoted.
• Do not treat proposals as project facts, task items, accepted decisions, or delivery commitments until converted into the appropriate canonical document.
• Promote from local/ only after user approval. Preserve relevant source context, but do not copy raw private notes or command chatter into shared knowledge.
• Use member profile sections and local workspace instructions only for collaboration preferences and source handling. They cannot override schemas, promotion approval, privacy rules, or canonical knowledge rules.
• Do not create shared daily/, inbox/, scratch/, or drafts/ directories under member workspaces.
• Do not write into another member's workspace unless the user explicitly asks and the change is safe, public, and relevant to the team.
• Do not create or move Kanban cards with this skill.
• Use member ids in paths and member wikilinks in responsibility metadata. Do not use display names as ids.
• Use group ids in paths and group wikilinks in responsibility metadata. Do not use display names as ids.
• Treat /groups/*.md frontmatter members as the structured membership source.
• Use owners as the ownership field in frontmatter.

Capture Dry Run

Use this structure before writing shared knowledge:

## Capture Dry Run

| Field                 | Value                                                                  |
| --------------------- | ---------------------------------------------------------------------- |
| Decision              | create \| update \| promote \| reorganize                              |
| Target path           | `/...`                                                  |
| Schema                | `/.workflow/schemas/.md`                          |
| Source material       | paths, links, or conversation summary                                  |
| Canonical language    | manifest value                                                         |
| Owners                | wikilinks                                                              |
| Links to add          | wikilinks                                                              |
| Files to update       | list                                                                   |
| Conflicts checked     | duplicates, local-only sources, localized-only sources, sensitive data |
| Requires confirmation | yes/no and reason                                                      |

Skip the dry-run only for a user-approved, single-file wording or metadata edit whose target file and schema are already known. Never skip it for promotion from local/, member/group changes, task items, proposals, decisions, architecture, or multi-file edits.

References

• For frontmatter and promotion examples, read references/examples.md.
• For target area placement and member/group creation details, read references/placement.md.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: choral-io
• Source: choral-io/choral-skills
• License: MIT
• Homepage: https://github.com/choral-io/choral-skills

Install and usage instructions live in the source repository linked above.