[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EGAT65V2X4BQN17044VDQ3":3,"skill-same:01M6EGAT65V2X4BQN17044VDQ3":95},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6EGAT65V2X4BQN17044VDQ3","ln-001-standards-researcher",null,"Research standards\u002Fpatterns via MCP Ref. Generates Standards Research for Story Technical Notes subsection. Reusable worker.","levalencia\u002Fagent-god-mode","levalencia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6962857?v=4","01M6EB0FZZ4BPQPC4HET4QY6NM","Luis Valencia ","01M6EB0G4HWHPWW0H9X7QKSAHP",3,"MIT","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-001-standards-researcher\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38],"researcher","standards","ln 001 standards researcher","MCP","research","notes","technical","Story","reusable","patterns","worker","via","2026-11-10 10:12:30",false,"---\nname: ln-001-standards-researcher\ndescription: Research standards\u002Fpatterns via MCP Ref. Generates Standards Research for Story Technical Notes subsection. Reusable worker.\nlicense: MIT\n---\n\n> **Paths:** File paths (`shared\u002F`, `references\u002F`, `..\u002Fln-*`) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.\n\n# Standards Researcher (Worker)\n\nThis skill researches industry standards and architectural patterns using MCP Ref to generate Standards Research for Story Technical Notes.\n\n## Purpose\n\nResearch industry standards, RFCs, and architectural patterns for a given Epic\u002FStory domain. Produce a Standards Research section (tables + links, no code) for insertion into Story Technical Notes.\n\n## When to Use This Skill\n\nThis skill should be used when:\n- Need to research standards and patterns BEFORE Story generation (ensures tasks follow industry best practices)\n- Epic Technical Notes mention specific standards requiring documentation (OAuth, OpenAPI, WebSocket)\n- Prevent situations where tasks use outdated patterns or violate RFC compliance\n- Reusable for ANY skill requiring standards research (ln-220-story-coordinator, ln-300-task-coordinator, ln-002-best-practices-researcher)\n\n**Who calls this skill:**\n- **ln-220-story-coordinator** (Phase 3) - research for Story creation\n- **ln-300-task-coordinator** (optional) - research for complex Stories\n- **Manual** - user can invoke directly for Epic\u002FStory research\n\n## Workflow\n\nThe skill follows a 7-phase workflow focused on standards and architectural patterns.\n\n```\nStack Detection → Identify → Ref Research → Existing Guides → Generate Research → Save to File → Return\n```\n\n### Phase 0: Stack Detection\n\n**Objective**: Determine project stack BEFORE research to filter queries.\n\n**Detection:**\n\n| Indicator | Stack | Query Prefix |\n|-----------|-------|--------------|\n| `*.csproj`, `*.sln` | .NET | \"C# ASP.NET Core\" |\n| `package.json` + `tsconfig.json` | Node.js | \"TypeScript Node.js\" |\n| `requirements.txt`, `pyproject.toml` | Python | \"Python\" |\n| `go.mod` | Go | \"Go Golang\" |\n| `Cargo.toml` | Rust | \"Rust\" |\n| `build.gradle`, `pom.xml` | Java | \"Java\" |\n\n**Process:**\n1. Check `context_store.TECH_STACK` if provided → use directly\n2. Else: Glob for indicator files in project root\n3. Store `detected_stack.query_prefix` for Phases 2-3\n\n**Output**: `detected_stack = {language, framework, query_prefix}`\n\n**Skip conditions**: If no stack detected → proceed without prefix (generic queries)\n\n---\n\n### Phase 1: Identify Libraries\n\n**Objective**: Parse Epic\u002FStory for libraries and technology keywords.\n\n**Process**:\n1. **Read Epic\u002FStory description** (provided as input)\n   - Parse Epic Technical Notes for mentioned libraries\u002Fframeworks\n   - Parse Epic Scope In for technology keywords (authentication, rate limiting, payments, etc.)\n   - Identify Story domain from Epic goal statement (e.g., \"Add rate limiting\" → domain = \"rate limiting\")\n\n2. **Extract library list**:\n   - Primary libraries (explicitly mentioned)\n   - Inferred libraries (e.g., \"REST API\" → FastAPI, \"caching\" → Redis)\n   - Filter out well-known libraries with stable APIs (e.g., requests, urllib3)\n\n3. **Determine Story domain**:\n   - Extract from Epic goal or Story title\n   - Examples: rate limiting, authentication, payment processing, file upload\n\n**Output**: Library list (3-5 libraries max) + Story domain\n\n**Skip conditions**:\n- NO libraries mentioned in Epic → Output empty Research Summary\n- Trivial CRUD operation with well-known libraries → Output empty Research Summary\n- Epic explicitly states \"research not needed\" → Skip\n\n---\n\n### Phase 2: MCP Ref Research\n\n**Objective**: Get industry standards and architectural patterns.\n\n**Process:**\n1. **Focus on standards\u002FRFCs:**\n   - Call `mcp__Ref__ref_search_documentation(query=\"[detected_stack.query_prefix] [story_domain] RFC standard specification\")`\n   - Example: `\"C# ASP.NET Core rate limiting RFC standard specification\"`\n   - Extract: RFC\u002Fspec references (OAuth 2.0 RFC 6749, OpenAPI 3.0, WebSocket RFC 6455)\n\n2. **Focus on architectural patterns:**\n   - Call `mcp__Ref__ref_search_documentation(query=\"[detected_stack.query_prefix] [story_domain] architectural patterns best practices\")`\n   - Example: `\"TypeScript Node.js authentication architectural patterns best practices\"`\n   - Extract: Middleware, Dependency Injection, Decorator pattern\n\n**Output:** Standards compliance table + Architectural patterns list\n\n---\n\n### Phase 3: MCP Ref Research\n\n**Objective**: Get industry standards and best practices.\n\n**Process**:\n1. **FOR EACH library + Story domain** combination:\n   - Call `mcp__Ref__ref_search_documentation(query=\"[detected_stack.query_prefix] [library] [domain] best practices {current_year}\")`\n   - Call `mcp__Ref__ref_search_documentation(query=\"[detected_stack.query_prefix] [domain] industry standards RFC\")`\n   - Example: `\"C# ASP.NET Core Polly rate limiting best practices {current_year}\"`\n\n2. **Extract from results** (NO CODE - text\u002Ftables only):\n   - **Industry standards** (RFC\u002Fspec references: OAuth 2.0, REST API, OpenAPI 3.0)\n   - **Common patterns** (do\u002Fdon't descriptions, anti-patterns to avoid)\n   - **Integration approaches** (middleware, dependency injection, decorators)\n   - **Security considerations** (OWASP compliance, vulnerability mitigation)\n   - **Official docs URLs** (link to stack-appropriate authoritative sources)\n\n3. **Store results** for Research Summary compilation\n\n**Output**: Standards compliance table (RFC\u002FStandard name, how to comply) + Best practices list\n\n---\n\n### Phase 4: Scan Existing Guides\n\n**Objective**: Find relevant pattern guides in docs\u002Fguides\u002F directory.\n\n**Process**:\n1. **Scan guides directory**:\n   - Use `Glob` to find `docs\u002Fguides\u002F*.md`\n   - Read guide filenames\n\n2. **Match guides to Story domain**:\n   - Match keywords (e.g., rate limiting guide for rate limiting Story)\n   - Fuzzy match (e.g., \"authentication\" matches \"auth.md\", \"oauth.md\")\n\n3. **Collect guide paths** for linking in Technical Notes\n\n**Output**: Existing guides list (relative paths from project root)\n\n---\n\n### Phase 5: Generate Standards Research\n\n**Objective**: Compile research results into Standards Research for Story Technical Notes subsection.\n\n**NO_CODE Rule:** No code snippets. Use tables + links to official docs only.\n\n**Format Priority:**\n```\n┌─────────────────────────────────────┐\n│ 1. TABLES + ASCII diagrams ← Priority │\n│ 2. Lists (enumerations only)        │\n│ 3. Text (last resort)               │\n└─────────────────────────────────────┘\n```\n\n**Output Format (Table-First):**\n\n```markdown\n## Standards Research\n\n**Standards compliance:**\n\n| Standard | Requirement | How to Comply | Reference |\n|----------|-------------|---------------|-----------|\n| RFC 6749 | OAuth 2.0 | Use PKCE for public clients | [RFC 6749](url) |\n| RFC 6585 | Rate Limiting | Return 429 + Retry-After | [RFC 6585](url) |\n\n**Architectural patterns:**\n\n| Pattern | When to Use | Reference |\n|---------|-------------|-----------|\n| Middleware | Request interception | [Official docs](url) |\n| Decorator | Cross-cutting concerns | [Official docs](url) |\n\n**Existing guides:**\n- [guide_path.md](guide_path.md) - Brief description\n```\n\n**Output:** Standards Research (Markdown string) for insertion into Story Technical Notes subsection\n\n**Important notes:**\n- Focus on STANDARDS and PATTERNS only (no library details - libraries researched at Task level)\n- Prefer official docs and RFC standards over blog posts\n- Link to stack-appropriate docs (Microsoft docs for .NET, MDN for JS, etc.)\n- If Standards Research is empty (no standards\u002Fpatterns) → Skip Phase 6, return \"No standards research needed\"\n\n---\n\n### Phase 6: Save Research to File\n\n**Objective**: Save Standards Research to standalone file for reusability and knowledge base.\n\n**MANDATORY**: All research MUST be saved to file, even if returned as string to caller.\n\n**Process:**\n\n1. **Determine next research number**:\n   - Glob for `docs\u002Fresearch\u002Frsh-*.md` files\n   - Extract numbers, find max\n   - Next number = max + 1 (or 001 if no files exist)\n\n2. **Generate filename**:\n   - Format: `rsh-{number:03d}-{slug}.md`\n   - Slug from `story_domain` (e.g., \"rate-limiting\", \"oauth-authentication\")\n   - Example: `rsh-042-rate-limiting.md`\n\n3. **Create research document** using template:\n\n```markdown\n# Standards Research: {Story Domain}\n\n**Created:** {ISO date}\n**Epic:** {Epic ID if available}\n**Research Type:** Standards & Architectural Patterns\n\n## Question\n\nWhat industry standards and architectural patterns apply to {story_domain}?\n\n## Context\n\n{Brief description from Epic\u002FStory}\n\n## Methodology\n\n- **Standards:** MCP Ref search for RFCs and specifications\n- **Patterns:** MCP Ref search for architectural patterns and best practices\n- **Stack:** {detected_stack.language} {detected_stack.framework}\n\n## Findings\n\n{Insert Standards Research content from Phase 5 here}\n\n## Conclusions\n\n{1-2 sentences summarizing key standards\u002Fpatterns that must be followed}\n\n## Next Steps\n\n- Reference this research in Story Technical Notes\n- Link from architecture.md if patterns affect system design\n- Create ADR if architectural decision needed\n\n## Sources\n\n{List of all MCP Ref search URLs with dates}\n```\n\n4. **Save file**:\n   - Write to `docs\u002Fresearch\u002F{filename}`\n   - If `docs\u002Fresearch\u002F` doesn't exist: create directory\n   - Validate file saved successfully\n\n5. **Update README** (if exists):\n   - Check for `docs\u002Fresearch\u002FREADME.md`\n   - If exists and has `\u003C!-- PLACEHOLDER -->`: append research entry\n   - Format: `- [{filename}]({filename}) - {one-line summary}`\n\n**Output**: File path (e.g., `docs\u002Fresearch\u002Frsh-042-rate-limiting.md`)\n\n**Skip conditions**:\n- Standards Research is empty → do not create file\n- Target directory missing and cannot be created → warn user, skip file creation\n\n---\n\n### Phase 7: Return Results\n\n**Return to calling skill** (ln-220, ln-310):\n\n1. **Standards Research string** (Markdown) for insertion into Story Technical Notes\n2. **File path** (string) for linking: `docs\u002Fresearch\u002Frsh-{NNN}-{slug}.md`\n\n**Format:**\n```\n{\n  \"standards_research\": \"\u003Cmarkdown string>\",\n  \"file_path\": \"docs\u002Fresearch\u002Frsh-042-rate-limiting.md\"\n}\n```\n\nIf calling skill expects only string (backward compatibility), return Standards Research string only. File is created regardless.\n\n---\n\n## Integration with Ecosystem\n\n**Called by:**\n- **ln-220-story-coordinator** (Phase 2) - research for ALL Stories in Epic\n- **ln-300-task-coordinator** (optional) - research for complex technical Stories\n\n**Dependencies:**\n- MCP Ref (ref_search_documentation) - industry standards and patterns\n- Glob (scan docs\u002Fguides\u002F)\n\n**Input parameters (from calling skill):**\n- `epic_description` (string) - Epic Technical Notes + Scope In + Goal\n- `story_domain` (string, optional) - Story domain (e.g., \"rate limiting\")\n\n**Output format:**\n- **Primary:** Markdown string (Standards Research for insertion into Story Technical Notes subsection)\n- **Secondary:** File path (string) for linking: `docs\u002Fresearch\u002Frsh-{NNN}-{slug}.md`\n- **Content:** Standards + Patterns (libraries researched at Task level)\n- **Note:** File is ALWAYS created (Phase 6); backward-compatible callers receive string only\n\n---\n\n## Time-Box and Performance\n\n**Time-box:** 15-20 minutes maximum per Epic\n\n**Performance:**\n- Research is done ONCE per Epic\n- Results reused for all Stories (5-10 Stories benefit from single research)\n- Parallel MCP calls when possible (Context7 + Ref)\n\n**Token efficiency:**\n- Context7: max 3000 tokens per library\n- Total: ~10,000 tokens for typical Epic (3-4 libraries)\n\n---\n\n## Critical Rules\n\n- **MANDATORY FILE CREATION:** All research MUST be saved to `docs\u002Fresearch\u002Frsh-{NNN}-{slug}.md` file (Phase 6); no exceptions\n- **NO_CODE:** Output contains tables and links to official docs only; no code snippets\n- **Format Priority:** Tables + ASCII diagrams first, lists second, text last resort\n- **Stack-aware queries:** All MCP Ref calls must include detected `query_prefix` (e.g., \"C# ASP.NET Core\")\n- **Standards over libraries:** Focus on RFCs and architectural patterns; library details are researched at Task level\n- **Time-box:** Maximum 15-20 minutes per Epic; research is done once and reused for all Stories\n\n## Definition of Done\n\n- Stack detected (or skipped if undetectable) and `query_prefix` set\n- Libraries and Story domain extracted from Epic\u002FStory description\n- MCP Ref research completed for standards\u002FRFCs and architectural patterns\n- Existing guides in `docs\u002Fguides\u002F` scanned and matched\n- Standards Research output generated in Markdown (tables + links, no code)\n- **Research saved to file:** `docs\u002Fresearch\u002Frsh-{NNN}-{slug}.md` created with all required sections\n- **README updated** (if `docs\u002Fresearch\u002FREADME.md` exists and has placeholder)\n- Output returned to calling skill (ln-220, ln-300): Standards Research string + file path\n\n## Reference Files\n\n**Tools:**\n- `mcp__Ref__ref_search_documentation()` - Search best practices and standards\n- `Glob` - Scan docs\u002Fguides\u002F directory\n\n**Templates:**\n- [research_guidelines.md](references\u002Fresearch_guidelines.md) - Research quality guidelines (official docs > blog posts, prefer LTS versions)\n\n- **MANDATORY READ:** `shared\u002Freferences\u002Fresearch_tool_fallback.md`\n\n---\n\n**Version:** 3.1.0\n**Last Updated:** 2026-02-14\n","> **Paths:** File paths (`shared\u002F`, `references\u002F`, `..\u002Fln-*`) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.\n\n# Standards Researcher (Worker)\n\nThis skill researches industry standards and architectural patterns using MCP Ref to generate Standards Research for Story Technical Notes.\n\n## Purpose\n\nResearch industry standards, RFCs, and architectural patterns for a given Epic\u002FStory domain. Produce a Standards Research section (tables + links, no code) for insertion into Story Technical Notes.\n\n## When to Use This Skill\n\nThis skill should be used when:\n- Need to research standards and patterns BEFORE Story generation (ensures tasks follow industry best practices)\n- Epic Technical Notes mention specific standards requiring documentation (OAuth, OpenAPI, WebSocket)\n- Prevent situations where tasks use outdated patterns or violate RFC compliance\n- Reusable for ANY skill requiring standards research (ln-220-story-coordinator, ln-300-task-coordinator, ln-002-best-practices-researcher)\n\n**Who calls this skill:**\n- **ln-220-story-coordinator** (Phase 3) - research for Story creation\n- **ln-300-task-coordinator** (optional) - research for complex Stories\n- **Manual** - user can invoke directly for Epic\u002FStory research\n\n## Workflow\n\nThe skill follows a 7-phase workflow focused on standards and architectural patterns.\n\n```\nStack Detection → Identify → Ref Research → Existing Guides → Generate Research → Save to File → Return\n```\n\n### Phase 0: Stack Detection\n\n**Objective**: Determine project stack BEFORE research to filter queries.\n\n**Detection:**\n\n| Indicator | Stack | Query Prefix |\n|-----------|-------|--------------|\n| `*.csproj`, `*.sln` | .NET | \"C# ASP.NET Core\" |\n| `package.json` + `tsconfig.json` | Node.js | \"TypeScript Node.js\" |\n| `requirements.txt`, `pyproject.toml` | Python | \"Python\" |\n| `go.mod` | Go | \"Go Golang\" |\n| `Cargo.toml` | Rust | \"Rust\" |\n| `build.gradle`, `pom.xml` | Java | \"Java\" |\n\n**Process:**\n1. Check `context_store.TECH_STACK` if provided → use directly\n2. Else: Glob for indicator files in project root\n3. Store `detected_stack.query_prefix` for Phases 2-3\n\n**Output**: `detected_stack = {language, framework, query_prefix}`\n\n**Skip conditions**: If no stack detected → proceed without prefix (generic queries)\n\n---\n\n### Phase 1: Identify Libraries\n\n**Objective**: Parse Epic\u002FStory for libraries and technology keywords.\n\n**Process**:\n1. **Read Epic\u002FStory description** (provided as input)\n   - Parse Epic Technical Notes for mentioned libraries\u002Fframeworks\n   - Parse Epic Scope In for technology keywords (authentication, rate limiting, payments, etc.)\n   - Identify Story domain from Epic goal statement (e.g., \"Add rate limiting\" → domain = \"rate limiting\")\n\n2. **Extract library list**:\n   - Primary libraries (explicitly mentioned)\n   - Inferred libraries (e.g., \"REST API\" → FastAPI, \"caching\" → Redis)\n   - Filter out well-known libraries with stable APIs (e.g., requests, urllib3)\n\n3. **Determine Story domain**:\n   - Extract from Epic goal or Story title\n   - Examples: rate limiting, authentication, payment processing, file upload\n\n**Output**: Library list (3-5 libraries max) + Story domain\n\n**Skip conditions**:\n- NO libraries mentioned in Epic → Output empty Research Summary\n- Trivial CRUD operation with well-known libraries → Output empty Research Summary\n- Epic explicitly states \"research not needed\" → Skip\n\n---\n\n### Phase 2: MCP Ref Research\n\n**Objective**: Get industry standards and architectural patterns.\n\n**Process:**\n1. **Focus on standards\u002FRFCs:**\n   - Call `mcp__Ref__ref_search_documentation(query=\"[detected_stack.query_prefix] [story_domain] RFC standard specification\")`\n   - Example: `\"C# ASP.NET Core rate limiting RFC standard specification\"`\n   - Extract: RFC\u002Fspec references (OAuth 2.0 RFC 6749, OpenAPI 3.0, WebSocket RFC 6455)\n\n2. **Focus on architectural patterns:**\n   - Call `mcp__Ref__ref_search_documentation(query=\"[detected_stack.query_prefix] [story_domain] architectural patterns best practices\")`\n   - Example: `\"TypeScript Node.js authentication architectural patterns best practices\"`\n   - Extract: Middleware, Dependency Injection, Decorator pattern\n\n**Output:** Standards compliance table + Architectural patterns list\n\n---\n\n### Phase 3: MCP Ref Research\n\n**Objective**: Get industry standards and best practices.\n\n**Process**:\n1. **FOR EACH library + Story domain** combination:\n   - Call `mcp__Ref__ref_search_documentation(query=\"[detected_stack.query_prefix] [library] [domain] best practices {current_year}\")`\n   - Call `mcp__Ref__ref_search_documentation(query=\"[detected_stack.query_prefix] [domain] industry standards RFC\")`\n   - Example: `\"C# ASP.NET Core Polly rate limiting best practices {current_year}\"`\n\n2. **Extract from results** (NO CODE - text\u002Ftables only):\n   - **Industry standards** (RFC\u002Fspec references: OAuth 2.0, REST API, OpenAPI 3.0)\n   - **Common patterns** (do\u002Fdon't descriptions, anti-patterns to avoid)\n   - **Integration approaches** (middleware, dependency injection, decorators)\n   - **Security considerations** (OWASP compliance, vulnerability mitigation)\n   - **Official docs URLs** (link to stack-appropriate authoritative sources)\n\n3. **Store results** for Research Summary compilation\n\n**Output**: Standards compliance table (RFC\u002FStandard name, how to comply) + Best practices list\n\n---\n\n### Phase 4: Scan Existing Guides\n\n**Objective**: Find relevant pattern guides in docs\u002Fguides\u002F directory.\n\n**Process**:\n1. **Scan guides directory**:\n   - Use `Glob` to find `docs\u002Fguides\u002F*.md`\n   - Read guide filenames\n\n2. **Match guides to Story domain**:\n   - Match keywords (e.g., rate limiting guide for rate limiting Story)\n   - Fuzzy match (e.g., \"authentication\" matches \"auth.md\", \"oauth.md\")\n\n3. **Collect guide paths** for linking in Technical Notes\n\n**Output**: Existing guides list (relative paths from project root)\n\n---\n\n### Phase 5: Generate Standards Research\n\n**Objective**: Compile research results into Standards Research for Story Technical Notes subsection.\n\n**NO_CODE Rule:** No code snippets. Use tables + links to official docs only.\n\n**Format Priority:**\n```\n┌─────────────────────────────────────┐\n│ 1. TABLES + ASCII diagrams ← Priority │\n│ 2. Lists (enumerations only)        │\n│ 3. Text (last resort)               │\n└─────────────────────────────────────┘\n```\n\n**Output Format (Table-First):**\n\n```markdown\n## Standards Research\n\n**Standards compliance:**\n\n| Standard | Requirement | How to Comply | Reference |\n|----------|-------------|---------------|-----------|\n| RFC 6749 | OAuth 2.0 | Use PKCE for public clients | [RFC 6749](url) |\n| RFC 6585 | Rate Limiting | Return 429 + Retry-After | [RFC 6585](url) |\n\n**Architectural patterns:**\n\n| Pattern | When to Use | Reference |\n|---------|-------------|-----------|\n| Middleware | Request interception | [Official docs](url) |\n| Decorator | Cross-cutting concerns | [Official docs](url) |\n\n**Existing guides:**\n- [guide_path.md](guide_path.md) - Brief description\n```\n\n**Output:** Standards Research (Markdown string) for insertion into Story Technical Notes subsection\n\n**Important notes:**\n- Focus on STANDARDS and PATTERNS only (no library details - libraries researched at Task level)\n- Prefer official docs and RFC standards over blog posts\n- Link to stack-appropriate docs (Microsoft docs for .NET, MDN for JS, etc.)\n- If Standards Research is empty (no standards\u002Fpatterns) → Skip Phase 6, return \"No standards research needed\"\n\n---\n\n### Phase 6: Save Research to File\n\n**Objective**: Save Standards Research to standalone file for reusability and knowledge base.\n\n**MANDATORY**: All research MUST be saved to file, even if returned as string to caller.\n\n**Process:**\n\n1. **Determine next research number**:\n   - Glob for `docs\u002Fresearch\u002Frsh-*.md` files\n   - Extract numbers, find max\n   - Next number = max + 1 (or 001 if no files exist)\n\n2. **Generate filename**:\n   - Format: `rsh-{number:03d}-{slug}.md`\n   - Slug from `story_domain` (e.g., \"rate-limiting\", \"oauth-authentication\")\n   - Example: `rsh-042-rate-limiting.md`\n\n3. **Create research document** using template:\n\n```markdown\n# Standards Research: {Story Domain}\n\n**Created:** {ISO date}\n**Epic:** {Epic ID if available}\n**Research Type:** Standards & Architectural Patterns\n\n## Question\n\nWhat industry standards and architectural patterns apply to {story_domain}?\n\n## Context\n\n{Brief description from Epic\u002FStory}\n\n## Methodology\n\n- **Standards:** MCP Ref search for RFCs and specifications\n- **Patterns:** MCP Ref search for architectural patterns and best practices\n- **Stack:** {detected_stack.language} {detected_stack.framework}\n\n## Findings\n\n{Insert Standards Research content from Phase 5 here}\n\n## Conclusions\n\n{1-2 sentences summarizing key standards\u002Fpatterns that must be followed}\n\n## Next Steps\n\n- Reference this research in Story Technical Notes\n- Link from architecture.md if patterns affect system design\n- Create ADR if architectural decision needed\n\n## Sources\n\n{List of all MCP Ref search URLs with dates}\n```\n\n4. **Save file**:\n   - Write to `docs\u002Fresearch\u002F{filename}`\n   - If `docs\u002Fresearch\u002F` doesn't exist: create directory\n   - Validate file saved successfully\n\n5. **Update README** (if exists):\n   - Check for `docs\u002Fresearch\u002FREADME.md`\n   - If exists and has `\u003C!-- PLACEHOLDER -->`: append research entry\n   - Format: `- [{filename}]({filename}) - {one-line summary}`\n\n**Output**: File path (e.g., `docs\u002Fresearch\u002Frsh-042-rate-limiting.md`)\n\n**Skip conditions**:\n- Standards Research is empty → do not create file\n- Target directory missing and cannot be created → warn user, skip file creation\n\n---\n\n### Phase 7: Return Results\n\n**Return to calling skill** (ln-220, ln-310):\n\n1. **Standards Research string** (Markdown) for insertion into Story Technical Notes\n2. **File path** (string) for linking: `docs\u002Fresearch\u002Frsh-{NNN}-{slug}.md`\n\n**Format:**\n```\n{\n  \"standards_research\": \"\u003Cmarkdown string>\",\n  \"file_path\": \"docs\u002Fresearch\u002Frsh-042-rate-limiting.md\"\n}\n```\n\nIf calling skill expects only string (backward compatibility), return Standards Research string only. File is created regardless.\n\n---\n\n## Integration with Ecosystem\n\n**Called by:**\n- **ln-220-story-coordinator** (Phase 2) - research for ALL Stories in Epic\n- **ln-300-task-coordinator** (optional) - research for complex technical Stories\n\n**Dependencies:**\n- MCP Ref (ref_search_documentation) - industry standards and patterns\n- Glob (scan docs\u002Fguides\u002F)\n\n**Input parameters (from calling skill):**\n- `epic_description` (string) - Epic Technical Notes + Scope In + Goal\n- `story_domain` (string, optional) - Story domain (e.g., \"rate limiting\")\n\n**Output format:**\n- **Primary:** Markdown string (Standards Research for insertion into Story Technical Notes subsection)\n- **Secondary:** File path (string) for linking: `docs\u002Fresearch\u002Frsh-{NNN}-{slug}.md`\n- **Content:** Standards + Patterns (libraries researched at Task level)\n- **Note:** File is ALWAYS created (Phase 6); backward-compatible callers receive string only\n\n---\n\n## Time-Box and Performance\n\n**Time-box:** 15-20 minutes maximum per Epic\n\n**Performance:**\n- Research is done ONCE per Epic\n- Results reused for all Stories (5-10 Stories benefit from single research)\n- Parallel MCP calls when possible (Context7 + Ref)\n\n**Token efficiency:**\n- Context7: max 3000 tokens per library\n- Total: ~10,000 tokens for typical Epic (3-4 libraries)\n\n---\n\n## Critical Rules\n\n- **MANDATORY FILE CREATION:** All research MUST be saved to `docs\u002Fresearch\u002Frsh-{NNN}-{slug}.md` file (Phase 6); no exceptions\n- **NO_CODE:** Output contains tables and links to official docs only; no code snippets\n- **Format Priority:** Tables + ASCII diagrams first, lists second, text last resort\n- **Stack-aware queries:** All MCP Ref calls must include detected `query_prefix` (e.g., \"C# ASP.NET Core\")\n- **Standards over libraries:** Focus on RFCs and architectural patterns; library details are researched at Task level\n- **Time-box:** Maximum 15-20 minutes per Epic; research is done once and reused for all Stories\n\n## Definition of Done\n\n- Stack detected (or skipped if undetectable) and `query_prefix` set\n- Libraries and Story domain extracted from Epic\u002FStory description\n- MCP Ref research completed for standards\u002FRFCs and architectural patterns\n- Existing guides in `docs\u002Fguides\u002F` scanned and matched\n- Standards Research output generated in Markdown (tables + links, no code)\n- **Research saved to file:** `docs\u002Fresearch\u002Frsh-{NNN}-{slug}.md` created with all required sections\n- **README updated** (if `docs\u002Fresearch\u002FREADME.md` exists and has placeholder)\n- Output returned to calling skill (ln-220, ln-300): Standards Research string + file path\n\n## Reference Files\n\n**Tools:**\n- `mcp__Ref__ref_search_documentation()` - Search best practices and standards\n- `Glob` - Scan docs\u002Fguides\u002F directory\n\n**Templates:**\n- [research_guidelines.md](references\u002Fresearch_guidelines.md) - Research quality guidelines (official docs > blog posts, prefer LTS versions)\n\n- **MANDATORY READ:** `shared\u002Freferences\u002Fresearch_tool_fallback.md`\n\n---\n\n**Version:** 3.1.0\n**Last Updated:** 2026-02-14\n",{"name":5,"license":15,"description":7},"main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fln-001-standards-researcher",1,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode","https:\u002F\u002Fgithub.com\u002Flevalencia","https:\u002F\u002Fmedium.com\u002F@luisevalencia","Microsoft MVP - Artificial Intelligence\r\nMachine Learning Enthusiast\r\n","2026-05-02 06:55:36",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add levalencia\u002Fagent-god-mode --skill ln-001-standards-researcher",{"tool":59,"command":60},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill ln-001-standards-researcher",{"tool":62,"command":63},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill ln-001-standards-researcher","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-001-standards-researcher\u002FSKILL.md",true,[67,73,77,81,85,91],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"examples\u002F3p-updates.md","REFERENCE","参考文档",3274,"https:\u002F\u002Fgithub.com\u002Fleexb-wp21-prog\u002FAzure-Ticket-Helpdesk\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fskills-main\u002Fskills-main\u002Fskills\u002Finternal-comms\u002Fexamples\u002F3p-updates.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"examples\u002Fcompany-newsletter.md",3295,"https:\u002F\u002Fgithub.com\u002Fleexb-wp21-prog\u002FAzure-Ticket-Helpdesk\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fskills-main\u002Fskills-main\u002Fskills\u002Finternal-comms\u002Fexamples\u002Fcompany-newsletter.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"examples\u002Ffaq-answers.md",2366,"https:\u002F\u002Fgithub.com\u002Fleexb-wp21-prog\u002FAzure-Ticket-Helpdesk\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fskills-main\u002Fskills-main\u002Fskills\u002Finternal-comms\u002Fexamples\u002Ffaq-answers.md",{"path":82,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":83,"sourceHtmlUrl":84},"examples\u002Fgeneral-comms.md",602,"https:\u002F\u002Fgithub.com\u002Fleexb-wp21-prog\u002FAzure-Ticket-Helpdesk\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fskills-main\u002Fskills-main\u002Fskills\u002Finternal-comms\u002Fexamples\u002Fgeneral-comms.md",{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"LICENSE.txt","LICENSE","许可证",11345,"https:\u002F\u002Fgithub.com\u002Fleexb-wp21-prog\u002FAzure-Ticket-Helpdesk\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fskills-main\u002Fskills-main\u002Fskills\u002Finternal-comms\u002FLICENSE.txt",{"path":92,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fresearch_guidelines.md",7284,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-001-standards-researcher\u002Freferences\u002Fresearch_guidelines.md",[96,118,151,178,204,232],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":39},"01M6EM8ES5M9J4S8N78NJST0YC","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fzarr-python\u002FSKILL.md",[],[103,104,105,106,107,108,109,110,111,112,113,114,115,116,117],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":133,"publishedAt":39},"01M6EM8AR6ZFKZ9YVW8TTG850Z","zabbix","Zabbix monitoring system automation via API and Python. Use when: (1) Managing hosts, templates, items, triggers, or host groups, (2) Automating monitoring configuration, (3) Sending data via Zabbix trapper\u002Fsender, (4) Querying historical data or events, (5) Bulk operations on Zabbix objects, (6) Maintenance window management, (7) User\u002Fpermission management","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fzabbix-api-skill\u002FSKILL.md",[124,127,128],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":129,"categoryName":130,"taxonomyType":131,"taxonomyTypeDesc":132},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[120,103,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,38,150],"automation","window management","monitoring","data","templates","api","system","operations","use","maintenance","objects","permission","bulk operations","triggers","host","events","bulk",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":39},"01M6EM6Q9JG846ECQY9A210A26","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fx-twitter-growth\u002FSKILL.md",[],[158,159,160,161,162,163,164,165,166,167,168,169,170,171,172,173,174,175,176,177],"twitter","x twitter growth","growth","competitive intelligence","search","analyzing","plan","marketing","web search","competitors","analyze","write","optimize","social","intelligence","viral","growth engine","mechanics","grow","competitive",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":39},"01M6EM3FQNPYNKPC4CV9TCVNGD","what-if-oracle","Run structured What-If scenario analysis with multi-branch possibility exploration. Use this skill when the user asks speculative questions like \"what if...\", \"what would happen if...\", \"what are the possibilities\", \"explore scenarios\", \"scenario analysis\", \"possibility space\", \"what could go wrong\", \"best case \u002F worst case\", \"risk analysis\", \"contingency planning\", \"strategic options\", or any question about uncertain futures. Also trigger when the user faces a fork-in-the-road decision, wants to stress-test an idea, or needs to think through consequences before committing.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fwhat-if-oracle\u002FSKILL.md",[],[185,186,187,188,189,190,191,192,193,194,195,196,142,197,198,199,200,201,202,203],"oracle","what if oracle","test","planning","ux","futures","risk","analysis","explore","decision","branch","question","exploration","options","stress-test","strategies","trigger","case","multi",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":208,"categories":209,"keywords":213,"publishedAt":39},"01M6EM08C06RGDYCJ86HAPK0FF","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fvercel-react-best-practices\u002FSKILL.md",[210],{"categoryNo":211,"categoryName":212,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[214,215,216,217,218,219,220,221,222,223,224,225,226,137,227,228,229,230,231,147],"react","vercel react best practices","best practices","react best practices","vercel","writing","performance","components","react components","guidelines","tasks","code","Optimization","Next.js","refactoring","performance optimization","next","pages",{"skillNo":233,"name":234,"nameZh":6,"description":235,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":236,"categories":237,"keywords":246,"publishedAt":39},"01M6EM00S13326QM08DTM94J6Z","venue-templates","Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fvenue-templates\u002FSKILL.md",[238,241,242,243],{"categoryNo":239,"categoryName":240,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":244,"categoryName":245,"taxonomyType":131,"taxonomyTypeDesc":132},"01JBSEEDCAT000000000000036","内容创作者",[138,247,31,223,248,249,250,251,252,253,254,169,255,256,257,258,259,260,117,261],"venue templates","NeurIPS","ICML","LaTeX","science","Bash","access","read","edit","proposals","Academic","requirements","formatting","journal","chi"]