docs

Launch blog-writer agent to create a technical blog post with interactive input collection

Configure docs plugin settings (base path, folder names for each document type)

백준 풀이 .py 파일을 분석하여 문제 정리 마크다운을 생성한다. 디렉토리 내 .py 파일이 여러 개면 배치/단일 선택을 묻고, 배치 선택 시 파일별 에이전트를 병렬 실행한다.

Launch daily-work-details-writer agent for detailed technical logs with interactive input collection

Launch portfolio-writer agent to create/update project portfolio with interactive input collection

Launch readme-architect agent to create/improve README.md

Launch daily-work-writer agent to generate work logs with interactive input collection

Use this agent when the user wants to write a blog post about a technical topic. This agent interactively collects topic, reference URLs, format, and writing style from the user, then creates well-structured, human-like blog posts.\n\n<example>\nContext: User wants to write a blog post.\nuser: "/blog"\nassistant: "blog-writer 에이전트를 실행합니다. 블로그 글 작성에 필요한 정보를 순차적으로 수집하겠습니다."\n</example>\n\n<example>\nContext: User wants to write about a specific topic.\nuser: "MCP에 대해 블로그 글 써줘"\nassistant: "blog-writer 에이전트로 MCP에 대한 블로그 글을 작성하겠습니다. 추가 정보를 수집합니다."\n</example>

Use this agent when the user wants to create a coding test problem write-up based on their Baekjoon (BOJ) solution. This agent reads the user's Python solution file, fetches the problem from Baekjoon, finds alternative solutions, generates AI solutions and feedback, then creates a structured markdown document. <example> Context: User wants to create a write-up for their Baekjoon solution. user: "/docs:cote" assistant: "cote-writer 에이전트를 실행합니다. 최신 py 파일을 분석하여 문제 정리 글을 작성하겠습니다." </example> <example> Context: User wants to document a specific problem. user: "백준 17609번 풀이 정리해줘" assistant: "cote-writer 에이전트로 17609번 문제 정리 글을 작성하겠습니다." </example>

Use this agent when the user needs to generate or update detailed technical work logs for personal reference based on git commit history. This agent should be used proactively in the following scenarios:\n\n<example>\nContext: User wants to create detailed technical logs for their project.\nuser: "프로젝트 상세 작업 기록 작성해줘"\nassistant: "I'll use the Task tool to launch the daily-work-details-writer agent to create detailed technical work logs based on git commit history."\n<task tool call to daily-work-details-writer>\n</example>\n\n<example>\nContext: User wants to document their implementation details.\nuser: "개발일지 작성해줘"\nassistant: "I'll use the daily-work-details-writer agent to analyze git commits and create detailed technical logs."\n<task tool call to daily-work-details-writer>\n</example>\n\n<example>\nContext: User wants to create detailed work logs for their project on specific directory.\nuser: "temp 폴더에 상세 작업 기록 생성해줘"\nassistant: "Let me use the daily-work-details-writer agent to create detailed technical logs from your recent commits on temp directory'."\n<task tool call to daily-work-details-writer>\n</example>\n\n<example>\nContext: End of work day and user wants to document technical details.\nuser: "오늘 한 작업 디테일하게 기록해둬야겠다"\nassistant: "I'll launch the daily-work-details-writer agent to create detailed technical logs with today's commits."\n<task tool call to daily-work-details-writer>\n</example>

Use this agent when the user wants to create or update a portfolio document for their current project. This includes scenarios where:\n\n- The user explicitly requests portfolio creation (e.g., "프로젝트 포트폴리오 만들어줘", "portfolio 작성해줘")\n- The user asks to document their project for showcase purposes\n- The user mentions updating existing portfolio documentation\n- After completing a significant project milestone and the user wants to document it\n\nExamples:\n\n<example>\nContext: User has completed a major feature and wants to document it in their portfolio.\nuser: "이번에 완성한 프로젝트를 포트폴리오로 정리해줘"\nassistant: "포트폴리오 작성을 위해 portfolio-writer 에이전트를 실행하겠습니다. 프로젝트 구조와 git 이력을 분석하여 포트폴리오를 생성하겠습니다."\n</example>\n\n<example>\nContext: User wants to update an existing portfolio with recent changes.\nuser: "최근 변경사항을 포트폴리오에 반영해줘"\nassistant: "portfolio-writer 에이전트를 사용하여 최근 커밋 이력을 분석하고 기존 포트폴리오를 업데이트하겠습니다."\n</example>

Use this agent when you need to create or improve a GitHub README.md file for your project. This agent is specifically designed for transforming raw project information into professional, visually compelling documentation that follows open-source best practices.\n\n**Examples:**\n\n<example>\nContext: User has just completed a new open-source CLI tool and needs a README.\nuser: "I've built a Rust-based file synchronization tool called SyncFast. It's really fast and supports both local and cloud storage. Can you help me create a README?"\nassistant: "I'll use the readme-architect agent to create a professional, visually compelling README for your SyncFast project."\n<Uses Task tool to launch readme-architect agent>\n</example>\n\n<example>\nContext: User wants to revamp an existing README that lacks visual appeal.\nuser: "My project's README is just plain text with no structure. Here's the current content: [content]. Can you make it look professional?"\nassistant: "Let me use the readme-architect agent to transform your README into a high-visual, well-structured document that follows GitHub best practices."\n<Uses Task tool to launch readme-architect agent>\n</example>\n\n<example>\nContext: User is starting a new project and wants guidance on documentation.\nuser: "I'm about to start a new web framework project. What should I include in my README?"\nassistant: "I'll launch the readme-architect agent to provide you with a comprehensive README template and guidance tailored to web framework projects."\n<Uses Task tool to launch readme-architect agent>\n</example>\n\n<example>\nContext: User mentions they need help documenting their project after completing features.\nuser: "Just finished implementing the core features of my data visualization library. Now I need to document it properly."\nassistant: "Perfect timing! I'll use the readme-architect agent to create a professional README that showcases your data visualization library's features with strong visual hierarchy and clear documentation."\n<Uses Task tool to launch readme-architect agent>\n</example>

Use this agent when the user needs to generate or update daily work logs based on git commit history. This agent should be used proactively in the following scenarios:\n\n<example>\nContext: User wants to create work logs for their project.\nuser: "프로젝트 업무일지 작성해줘"\nassistant: "I'll use the Task tool to launch the daily-work-writer agent to create daily work logs based on git commit history."\n<task tool call to daily-work-writer>\n</example>\n\n<example>\nContext: User mentions they need to report their work progress.\nuser: "이번주 작업 내용 정리 좀 해줘"\nassistant: "I'll use the daily-work-writer agent to analyze git commits and create formatted work logs for reporting."\n<task tool call to daily-work-writer>\n</example>\n\n<example>\nContext: User wants to create work logs for their project on specific directory.\nuser: "temp 폴더에 업무일지 생성해줘"\nassistant: "Let me use the daily-work-writer agent to create professional work logs from your recent commits on temp directory'."\n<task tool call to daily-work-writer>\n</example>\n\n<example>\nContext: End of work day and user wants to document progress.\nuser: "오늘 한 작업들 기록해둬야겠다"\nassistant: "I'll launch the daily-work-writer agent to update your work logs with today's commits."\n<task tool call to daily-work-writer>\n</example>

3 hooks across 2 events