Loading...
Loading...
Found 116 Skills
Use when the user wants to view, add, update, or close issues. Manages ISSUES.md for this project.
Chapter 4 (사업 기대효과) 작성 가이드 - 템플릿 및 요구사항 통합
Archive session learnings, debugging solutions, and deployment logs to .archive/yyyy-mm-dd/ as indexed markdown with searchable tags. Use when completing a significant task, resolving a tricky bug, deploying, or when the user says "archive this". Maintains .archive/MEMORY.md index for cross-session knowledge reuse.
Maintain organized project documentation with metadata headers. Update existing docs before creating new ones. Use when writing or editing any project documentation.
Update the project README.md with comprehensive documentation based on the current codebase state. Use when the README needs updating or is outdated.
Creates detailed technical specifications for software projects covering requirements, architecture, APIs, and testing strategies. Use when planning features, documenting system design, or creating architecture decision records.
PROACTIVELY track and document project design decisions without being asked. Activate automatically when detecting architecture discussions, implementation decisions, pattern choices, library selections, or any technical decisions. Also use when user explicitly says "record this", "what's our design status", or equivalent. Do NOT wait for user to ask - record important decisions immediately.
[Manual Only] Record project learnings in FORyusuke.md. Structurally append lessons learned, pitfalls, debugging stories, and improvement points obtained during the session. It only works when explicitly called via /teach (it will not be triggered automatically in normal work).
Эксперт по README файлам. Используй для создания документации проектов, badges, installation guides и usage examples.
Requirements Analysis SKILL, which can further interact with users to clarify requirements
Product design, feature planning, and technical architecture for new projects. Explores the problem space through deep requirements gathering, suggests creative features, makes architecture decisions, and produces a structured MVP plan with scope boundaries, a future roadmap, and a deliverable tracker. Uses plan mode for deliberate thinking before writing any artifacts. Use when the user says "mvp", "plan a product", "design features", "what should I build", "feature planning", "scope an MVP", or describes a product they want to plan.
Initialize a new project with deep context gathering and PROJECT.md