القائمة
Archive a completed morkit change. Moves it from active to archive subfolder and updates .meta.json. Use when implementation is complete and merged.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | archive |
| description | Archive a completed morkit change. Moves it from active to archive subfolder and updates .meta.json. Use when implementation is complete and merged. |
| license | MIT |
Archive a completed change by moving it from ${MORKIT_ROOT:-morkit/output/spec}/<name>/ to ${MORKIT_ROOT:-morkit/output/spec}/archive/<name>/ and updating .meta.json.archived + archived_at.
Input: Optionally specify a change name. If omitted, list active changes and prompt.
Steps
Select the change to archive
List active changes (excluding archive/):
bash "${MORKIT_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}/scripts/list-changes.sh" --json
If no name was provided, use AskUserQuestion tool to let the user pick.
Show only changes whose tasks.md is fully ticked (no remaining - [ ]) by default; surface partial ones with a warning.
Do NOT auto-select.
Sanity check completion
pending=$(grep -cE '^[[:space:]]*-[[:space:]]+\[[[:space:]]\]' "$CHANGE_DIR/tasks.md" || echo 0)
$pending > 0, ask via AskUserQuestion whether to archive anyway.Docs bridge gate (soft — only when docs-hero is set up)
This change's proposal/design/tasks/spec only reach docs/ via the
docs bridge. Once archived, the change is out of bridge scope. So before
moving, offer to bridge — but only if the project actually uses docs-hero
(otherwise skip silently; never force a docs-hero dependency on spec-only users):
# Gate condition: docs-hero venv + project meta both present
VENV="${HOME}/.claude/plugins/data/docs-hero/.venv"
if [ -d "$VENV" ] && [ -f "${PWD}/.docs-hero-meta.json" ]; then
echo "docs-hero in use → offer bridge (AskUserQuestion below)"
else
echo "docs-hero not set up → skip gate, archive directly"
fi
If the gate condition holds, use AskUserQuestion:
"Change <name> sắp được archive. Bridge nội dung vào docs/ trước không?
(sau khi archive, WHAT/WHY của change không vào được docs/ nữa)"
Bridge trước (khuyến nghị) → run /morkit:docs-update --from-openspec <name>
(preserves manual edits via the diff engine), then continue to the move.Archive luôn → skip the bridge, continue.Hủy → abort archive (do not move).If the gate condition is false, skip this step entirely.
Move to archive
ROOT="${MORKIT_ROOT:-morkit/output/spec}"
mkdir -p "$ROOT/archive"
mv "$ROOT/<name>" "$ROOT/archive/<name>"
Update .meta.json
META="$ROOT/archive/<name>/.meta.json"
tmp="$(mktemp)"
jq --arg ts "$(date -u +'%Y-%m-%dT%H:%M:%SZ')" \
'.archived = true | .archived_at = $ts' \
"$META" > "$tmp" && mv "$tmp" "$META"
Report
✓ Archived <name>
From: <root>/<name>/
To: <root>/archive/<name>/
Archived at: <ts>
Guardrails
mv only.archive/<name> exists, ask.MORKIT_ROOT env.Sync task changes into a convention-driven knowledge pack (catalog.json + repos/*.md) and keep a weekly ledger of synced tasks. Manual, batch cadence — run by PM/team lead. Scans gRPC (.proto), REST (Gin), models (GORM), Makefile from source; human-gated via checkbox proposal. No prose auto-edits.
Generate or update full project documentation suite (SRS / API / DB / system-architecture / code-standards / codebase-summary / design-guidelines — user picks via /morkit:init multi-select gate). Orchestrates 7 sub-skills with conflict-minimal updates from OpenSpec changes, brainstorm plans, or codebase scans. Standards: BrSE ITO Japan (SRS), arc42-lite (arch), Conventional Commits (standards), MADR (guidelines). Supports init / update / sync.
Bridge skill — author a valid ProjectModel JSON (per normalized_schema) from greenfield inputs (parsed customer docs + brainstorm report + user-story list + risk register + clarification answers), then validate it so /morkit:init can render docs/srs.md and friends with no hand-authored JSON. The missing brainstorm→init link for the greenfield pipeline.
Generate or update Software Requirements Specification (SRS) following BrSE standards for ITO Japan. Renders the BrSE template-updated structure (13 sections + 2 appendices: Doc Control, Overview, Business Flow with UC detail, FR detail, Business Rules, Roles & Permissions, NFR with IPA-6 categories + Security/PII, Data Items with retention, External Interfaces, Reports, Acceptance/UAT, Traceability, Open Q&A, Constraints/Assumptions/Risks, Screen Index, Glossary). Init mode generates srs.md + per-screen specs from ProjectModel JSON; update mode applies a Delta to existing docs preserving manual edits.
Stateful guide for /morkit:greenfield — walks the BA/BrSE documentation pipeline G0→G7, runs the owning skill per stage, enforces the 4 human gates, and resumes from state.json. Thin glue: holds NO business logic — every stage delegates to an existing skill (brainstorming, generate-user-stories, gap-risk-analysis, clarification-loop, build-project-model) or to /morkit:init for the final SRS + design docs. Turns customer docs into a validated ProjectModel and a full docs/ set with no hand-authored JSON.
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.