Skip to content

feat: add Mastery skills — project memory across sessions (/mastery-status, /mastery-init, /mastery-plan, /mastery-handoff)#112

Open
RajeshYukta wants to merge 2 commits intogarrytan:mainfrom
RajeshYukta:mastery-status
Open

feat: add Mastery skills — project memory across sessions (/mastery-status, /mastery-init, /mastery-plan, /mastery-handoff)#112
RajeshYukta wants to merge 2 commits intogarrytan:mainfrom
RajeshYukta:mastery-status

Conversation

@RajeshYukta
Copy link

@RajeshYukta RajeshYukta commented Mar 16, 2026

What

Four new skills that bring the Mastery development lifecycle framework to gstack:

Skill What it does
/mastery-status Reads project docs and reports: active feature, task progress, last session note, what to pick up next
/mastery-init Bootstraps Mastery in any project — creates docs skeleton, runs project discussion, builds roadmap
/mastery-plan Plans a feature end-to-end: discussion → architecture → tasks → testplan
/mastery-handoff Writes a session handoff note so the next session (human or AI) starts instantly

Why

AI coding agents lose all context between sessions. Every new conversation starts cold — "what were we building? where did we stop?" Mastery solves this with structured docs that act as project memory.

These four skills give any gstack user a complete project lifecycle:

  1. Init a project with structured docs
  2. Plan each feature with discussion, architecture, and tasks
  3. Check status at the start of each session
  4. Hand off cleanly at the end of each session

How it works

Each skill follows standard gstack conventions:

  • YAML frontmatter with allowed-tools
  • {{PREAMBLE}} template placeholder
  • AskUserQuestion with re-ground / simplify / recommend / options pattern
  • Self-contained — no external dependencies, just Markdown

/mastery-status is read-only (no Write/Edit tools). The other three use Write/Edit to create and update Mastery docs.

Files changed

mastery-status/SKILL.md.tmpl    # Status reporting (read-only)
mastery-status/SKILL.md         # Generated
mastery-init/SKILL.md.tmpl      # Project bootstrapping
mastery-init/SKILL.md           # Generated
mastery-plan/SKILL.md.tmpl      # Feature planning
mastery-plan/SKILL.md           # Generated
mastery-handoff/SKILL.md.tmpl   # Session handoff
mastery-handoff/SKILL.md        # Generated
scripts/gen-skill-docs.ts       # +4 template paths in findTemplates()
README.md                       # +4 rows in skill table

Testing

Tested /mastery-status against a live Mastery project (the Mastery framework itself — 15 features, 12 complete). Correctly detected project, loaded context, identified active features, and produced structured status report.

All skills use only {{PREAMBLE}} (no browse-specific placeholders), keeping template processing straightforward.

… projects

Adds a new skill that reads Mastery framework docs (project-context,
project-roadmap, feature tasks, changelog) and outputs a structured
status report: active feature, task progress, last session note, and
next steps. Gives Claude project memory across sessions.

- mastery-status/SKILL.md.tmpl: skill template with {{PREAMBLE}}
- mastery-status/SKILL.md: generated output
- scripts/gen-skill-docs.ts: registered in findTemplates()
- README.md: added /mastery-status to skill table

Works on any project using Mastery (github.com/RAiWorks/MASTERY.md).
Read-only skill — no Write/Edit tools. Zero new dependencies.
Complete Mastery skill suite for gstack:
- /mastery-init: bootstrap Mastery framework in any project
- /mastery-plan: create feature planning docs (discuss, design, plan)
- /mastery-handoff: write session handoff notes for context continuity

All skills follow gstack conventions: YAML frontmatter, PREAMBLE,
AskUserQuestion pattern, self-contained Markdown.
@RajeshYukta RajeshYukta changed the title feat: add /mastery-status skill — project memory across sessions feat: add Mastery skills — project memory across sessions (/mastery-status, /mastery-init, /mastery-plan, /mastery-handoff) Mar 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant