تشغيل أي مهارة في Manus بنقرة واحدة

ابدأ الآن

memory-propose-confirm

النجوم٢

التفرعات٠

آخر تحديث١ يوليو ٢٠٢٦ في ٢١:٠٥

This skill should be used by the kon orchestrator when saving memory — from

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

dentiny

dentiny/kon

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

المهن الحاسوبية الأخرىمهن الحاسوب والرياضيات·SOC 15-1299

SKILL.md

readonly

name	memory-propose-confirm
description	This skill should be used by the kon orchestrator when saving memory — from

Memory Propose Confirm Flow

Owner: orchestrator Consumers: pipeline commands that end with retro (see skills/session-retro) plus mid-session propose from /kon:team, /kon:quick, /kon:debug.

Core principles (always): follow skills/core-principles — propose only evidence-backed entries; ask before saving ambiguous lessons.

Saving is propose + retro only (human confirm each write). Browse stored entries with cat on the two MEMORY.md indexes.

Storage paths

Scope	Directory	Index
public	`~/.kon/public/memory/`	`MEMORY.md`
repo	`~/.kon/projects/<repo-name>/memory/`	`MEMORY.md`

Ensure dirs exist before write:

python3 $KON_ROOT/hooks/_kon_paths.py public-memory
python3 $KON_ROOT/hooks/_kon_paths.py project-memory

Trigger: agent `## Memory propose`

When 📝 Mio or 🎶 Yui output contains ## Memory propose (outside code fences — see fence rule below), run confirm flow before the next pipeline step.

Required fields: name / slug / description / body / type / rationale. Missing any → skip with one line: "Memory propose detected but format incomplete — skipped."

Confirm flow

Format check (agent propose) or build candidate (session retro).
Show both indexes — print paths to public and repo MEMORY.md if they exist.
Print summary — type, name, description, rationale; suggest scope:
- public — user prefs, cross-repo habits, language, feedback
- repo — this repo's paths, tooling, local conventions User may override.
Ask user — Save to public / Save to repo / Edit / Skip.
On Save or Edit → write entry (step below).
On Skip → continue main flow, write nothing.

Write entry

On confirmed save:

Resolve target dir from scope (public or repo).
If <slug>.md already exists → ask: Overwrite / Rename slug / Cancel.
Write <slug>.md:

---
name: <name>
description: <description>
type: <user|feedback|project|reference>
---

<body>

Append to that scope's MEMORY.md (skip if an identical index line already present):

- [<name>](<slug>.md) — <description>

Print: Saved [public|repo] <name> → <path>.

Rollback on failure: if index append fails after entry write, remove the new entry file and report error.

Fence-tracking rule (agent propose only)

Only detect ## Memory propose outside code fences. Track triple-backtick count from output start; inside a fence (odd count), ignore the heading.

Memory types

Type	Typical scope	When to use
`user`	public	Personal preferences, language, identity
`project`	repo (sometimes public)	Repo conventions, tool choices, patterns
`feedback`	public	Process feedback ("reviews too long")
`reference`	either	URLs, docs, specs

Relationship to retro

Two save paths only (both require human confirm):

When	Trigger
Mid-session	Mio/Yui `## Memory propose` → this skill
End of pipeline	Session retro (after `/kon:summarize`) → this skill

Do not re-propose entries the user already saved this session.

Automatic retro at session close is the primary catch-all; propose handles explicit mid-session signals.

المزيد من هذا المستودع

نفس المستودع

design-debate

dentiny/kon

Multi-agent design argument — Azusa challenges Mugi's plan, Mugi revises. Used by /kon:design after exploration and initial plan draft.

2026-07-062

kon

dentiny/kon

Multi-agent software engineering workflow. Use this skill whenever the user types a /kon: command — including /kon:team, /kon:design, /kon:quick, /kon:debug, /kon:ask, /kon:review, /kon:review-pr, /kon:hunt, /kon:gc, /kon:research, /kon:describe-issue, /kon:begin, /kon:finish, /kon:summarize, /kon:retro, /kon:address-comments, /kon:todo, /kon:understand-codebase. Orchestrates specialized agents: Azusa (explorer), Jun (researcher), Mugi (planner), Yui (implementer), Mio (reviewer), Sawako (cleaner), Nodoka (summarizer).

2026-07-062

memory-loading

dentiny/kon

This skill should be used by all kon agents at startup, before beginning work, to load relevant memory from public and repo indexes with relevance-based ordering and a 10-entry cap. Consumers: Azusa, Mugi, Mio, Jun, and any future memory-reading agent.

2026-07-062

repo-skill

dentiny/kon

Convention for per-repo skill directories at ~/.kon/projects/<repo-name>/skills/<name>/SKILL.md. Each named subdirectory is one skill. Agents load all SKILL.md files as the first step before memory entries.

2026-07-062

ask-dont-guess

dentiny/kon

When requirements, code behavior, root cause, or review scope is unclear — ask the user before proceeding. Never invent facts, assumptions, or fixes. Applies to every kon stage and every agent.

2026-07-062

interactive-session

dentiny/kon

Route plain-text user messages while a /kon:begin session is open. Reuse the same session JSON — never init a second session for sub-turns.

2026-07-062

name	memory-propose-confirm
description	This skill should be used by the kon orchestrator when saving memory — from

Memory Propose Confirm Flow

Owner: orchestrator Consumers: pipeline commands that end with retro (see skills/session-retro) plus mid-session propose from /kon:team, /kon:quick, /kon:debug.

Core principles (always): follow skills/core-principles — propose only evidence-backed entries; ask before saving ambiguous lessons.

Saving is propose + retro only (human confirm each write). Browse stored entries with cat on the two MEMORY.md indexes.

Storage paths

Scope	Directory	Index
public	`~/.kon/public/memory/`	`MEMORY.md`
repo	`~/.kon/projects/<repo-name>/memory/`	`MEMORY.md`

Ensure dirs exist before write:

python3 $KON_ROOT/hooks/_kon_paths.py public-memory
python3 $KON_ROOT/hooks/_kon_paths.py project-memory

Trigger: agent `## Memory propose`

When 📝 Mio or 🎶 Yui output contains ## Memory propose (outside code fences — see fence rule below), run confirm flow before the next pipeline step.

Required fields: name / slug / description / body / type / rationale. Missing any → skip with one line: "Memory propose detected but format incomplete — skipped."

Confirm flow

Format check (agent propose) or build candidate (session retro).
Show both indexes — print paths to public and repo MEMORY.md if they exist.
Print summary — type, name, description, rationale; suggest scope:
- public — user prefs, cross-repo habits, language, feedback
- repo — this repo's paths, tooling, local conventions User may override.
Ask user — Save to public / Save to repo / Edit / Skip.
On Save or Edit → write entry (step below).
On Skip → continue main flow, write nothing.

Write entry

On confirmed save:

Resolve target dir from scope (public or repo).
If <slug>.md already exists → ask: Overwrite / Rename slug / Cancel.
Write <slug>.md:

---
name: <name>
description: <description>
type: <user|feedback|project|reference>
---

<body>

Append to that scope's MEMORY.md (skip if an identical index line already present):

- [<name>](<slug>.md) — <description>

Print: Saved [public|repo] <name> → <path>.

Rollback on failure: if index append fails after entry write, remove the new entry file and report error.

Fence-tracking rule (agent propose only)

Only detect ## Memory propose outside code fences. Track triple-backtick count from output start; inside a fence (odd count), ignore the heading.

Memory types

Type	Typical scope	When to use
`user`	public	Personal preferences, language, identity
`project`	repo (sometimes public)	Repo conventions, tool choices, patterns
`feedback`	public	Process feedback ("reviews too long")
`reference`	either	URLs, docs, specs

Relationship to retro

Two save paths only (both require human confirm):

When	Trigger
Mid-session	Mio/Yui `## Memory propose` → this skill
End of pipeline	Session retro (after `/kon:summarize`) → this skill

Do not re-propose entries the user already saved this session.

Automatic retro at session close is the primary catch-all; propose handles explicit mid-session signals.

memory-propose-confirm

Memory Propose Confirm Flow

Storage paths

Trigger: agent ## Memory propose

Confirm flow

Write entry

Fence-tracking rule (agent propose only)

Memory types

Relationship to retro

المزيد من هذا المستودع

المزيد من هذا المستودع

Memory Propose Confirm Flow

Storage paths

Trigger: agent ## Memory propose

Confirm flow

Write entry

Fence-tracking rule (agent propose only)

Memory types

Relationship to retro

Trigger: agent `## Memory propose`

Trigger: agent `## Memory propose`