Menu
Read the project wiki (vault/) before starting any non-trivial task. Surfaces relevant decisions, ownership, incidents, and glossary entries for the task at hand.
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 | query-wiki |
| description | Read the project wiki (vault/) before starting any non-trivial task. Surfaces relevant decisions, ownership, incidents, and glossary entries for the task at hand. |
Before touching the code, check what the team already knows.
vault/INDEX.md. Note relevant pages.Wiki context for <task>:
- [decisions/ADR-023-rate-limit.md] Current rate limit is token-bucket at Redis, 100/min per user
- [services/api.md] /api/v2/checkout is owned by @alice, SLA 99.9%
- [incidents/2025-12-03-double-charge.md] Related incident — watch for idempotency
- Nothing in vault about <specific-subtopic>; proceeding without prior context.