ringreceiving-code-review
Review reception protocol - requires technical verification before implementing suggestions. Prevents performative agreement and blind implementation.
Discover tools real estate legal skills, compare source repositories and read the instructions for each workflow.
Review reception protocol - requires technical verification before implementing suggestions. Prevents performative agreement and blind implementation.
Gate 4: API contracts document - defines component interfaces and data contracts before protocol/technology selection. Large Track only.
Gate 6: Technology choices document - explicit, versioned, validated technology selections with justifications. Large Track only. HARD BLOCK: Must load Ring Standards and PROJECT_RULES.md before proceeding.
Write feature plan with tasks. HOUSTON convenes planning council, synthesizes their input, and guides user through approval stages.
Create pre-registration documents for research transparency. Use when: (1) Before data collection, (2) Grant submissions, (3) Ensuring reproducibility, (4) Meeting open science standards, (5) Preventing HARKing...
Skill for creating and editing Architecture Decision Records (ADRs). Use when requests involve "create ADR", "record architecture decision", or "document design decisions". Supports creating new ADRs, updating...
Freight brokerage industry terminology and domain concepts. Use when working with laneweaverTMS to understand loads, tenders, carriers, accounts, facilities, stops, financial terms, status workflows, equipment...
When you need to understand the project's core mandate, operational rules, or "Constitution". Use this skill to align with the project's identity and strict coding standards.
PR を承認(approve)する。「PR 承認」「PR を approve」「approve して」「PR を通す」「LGTM」「PR OK」「マージ許可」などで起動。レビュー後に承認コメントを投稿。
This skill should be used when the user asks "when to transition phases", "move to active", "exit criteria", "what phase comes next", "how to complete a task", "transition to completed", "mark as blocked", "pha...
Operational rules for Interlock enforcement and receipts
Generate a quick compliance checklist from the Four Learning Design Pillars. Use when users want a practical checklist for reviewing content, a quick audit tool, or verification questions for specific pillars.
Never claim completion without fresh verification evidence
Architecture Decision Records (ADRs) for documenting technical decisions. Use when creating, updating, or reviewing architecture decisions. Triggers on discussions about technical choices, trade-offs, or "why d...
Continuation format reference for GSD sessions
This skill should be used when the user asks to "analyze regulations", "regulatory landscape", "compliance requirements", "legal considerations", "regulatory risk", "industry regulations", "compliance analysis"...
Multi-tier LLM routing for cost optimization in the BidDeed.AI ecosystem. Routes tasks to appropriate model tier based on complexity, achieving 90% FREE tier processing. Use when making API calls, selecting mod...
Unified database operations for BidDeed.AI and Life OS ecosystems. Use when: (1) logging insights, activities, or learning sessions, (2) querying historical data from any table, (3) user says "log this" or "...
The Architect of the PM Brain. Generates executive-ready, FAANG-quality Product Requirements Documents and feature specifications. Use for
Synthesize strategic roadmaps and document key decisions.
Generate Product Requirement Documents.
ACGME regulatory compliance expertise for medical residency scheduling. Use when validating schedules, checking work hour limits, supervision ratios, or answering compliance questions. Integrates with MCP valid...
Analyze swap compatibility and safety. Use when evaluating proposed schedule swaps to ensure they maintain ACGME compliance and operational coverage.
ACGME & institutional rule checking with systematic audit workflows, historical analysis, and violation remediation. Use for compliance audits, violation investigation, and regulatory reporting.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.