Menu
Maintain the project wiki in vault/. Use at the end of any session that produced a decision, fact, or state change. Extracts entities, updates topic pages, adds cross-links, never deletes. Pairs with the post_cascade_response_with_transcript hook.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Analyzes the extracted story document, capturing capability, acceptance criteria, edge cases, dependencies and open design questions. Use after extracting a story from a user request, to clarify the stories intended and likley imact. Use before designing the implementation.
Discovers the current application reality BEFORE designing or implementing. Surfaces relevant ADRs, existing code patterns, and target architecture.
Design the implementation of a new user story based on the current application reality, and analysis of the proposed user story.
Design comprehensive test cases for a given set of requirements. Use before starting TDD to plan coverage.
Drafts a high-level implementation plan based on the extracted story document
Extract a user story from a given document or text, into a json format
| name | update-wiki |
| description | Maintain the project wiki in vault/. Use at the end of any session that produced a decision, fact, or state change. Extracts entities, updates topic pages, adds cross-links, never deletes. Pairs with the post_cascade_response_with_transcript hook. |
After a session, update the project's vault/ so future sessions have the context.
The session did at least one of:
vault/decisions/ADR-NNN.mdvault/people/<name>.md + link from vault/services/<svc>.mdvault/incidents/YYYY-MM-DD-<short>.md with root cause + fix + invariant to add to AGENTS.mdvault/glossary.mdIf none of those happened, output "no wiki updates needed" and stop.
vault/INDEX.md to know the current shape of the wiki.[[wikilinks]] between entities. If you reference a page that doesn't exist, create a stub with a "TODO" note.> **Stale as of YYYY-MM-DD:** ... and add the new section below.vault/INDEX.md with any new pages.vault/decisions/ before picking a number.# ADR-NNN: <Decision title>
**Status:** Proposed | Accepted | Deprecated | Superseded by ADR-XXX
**Date:** YYYY-MM-DD
**Author:** <name or @role>
## Context
Why are we deciding this now? What forces are at play?
## Decision
What are we doing?
## Consequences
### Positive
-
### Negative
-
### Neutral / Follow-up
-
## Alternatives Considered
- **<Alternative 1>** — rejected because...
- **<Alternative 2>** — rejected because...
# YYYY-MM-DD: <One-line title>
**Severity:** SEV1 | SEV2 | SEV3
**Duration:** X hours
**Customer impact:** <facts, numbers>
## Timeline
- HH:MM — first symptom observed
- HH:MM — on-call paged
- HH:MM — mitigation started
- HH:MM — resolved
## Root cause
One paragraph. Factual, not blame-assigning.
## Contributing factors
- Factor 1
- Factor 2
## What went well
-
## What could have gone better
-
## Action items
- [ ] **<Owner>** — <action> — by <date>
## Invariant to add to AGENTS.md
(If this incident reveals a rule that should be constitutional, write it here and add to AGENTS.md.)