Loading...
Loading...
Found 127 Skills
Generate various types of documents based on the current project/code, supporting four types: thesis chapters, project sorting, key issues, and resume project descriptions. Use this when the user mentions generating thesis chapters, project sorting, technical difficulties, or resume project descriptions.
Generate comprehensive OpenSpec specifications directly from the current project state. Use when the user wants to create or populate main specs by analyzing existing code, documentation, AGENTS.md, GitHub issues, and pull requests — without going through the change/proposal workflow. Ideal for bootstrapping specs on a project that already has working code but no specs yet, or for refreshing specs to match the current implementation.
스프린트 내 모든 에픽이 완료된 후 스프린트 문서를 아카이빙한다. 문서 이동, changelog 업데이트, git commit을 자동으로 수행한다.
Clarify and compile project technical solutions. Use this when users need to determine the overall implementation approach, key technology trade-offs, module and file responsibilities, compatibility and verification boundaries for a problem, bug, function change, or existing requirement in combination with the current project, or when they need to create a technical document that can be understood by product, development, and testing teams and used for subsequent work. No prior requirement document is required, and it does not cover task breakdown, coding implementation, or project acceptance.
Write and maintain a CHANGELOG that stays useful months later — as a decision log, not a commit dump. Use when setting up a changelog for a project; after any code change in a project that has one; when preparing a release; or when the user asks why something was built the way it is and the answer is not in the code. Do not use for commit messages, PR descriptions, or user-facing release notes — those are different formats with different readers.
Generate or update project memory for AI agents — default to AGENTS.md, support agent-specific targets such as CLAUDE.md, and keep sibling memory files synchronized while capturing stable architecture, conventions, and operational knowledge
Produce the smallest user-facing report that preserves every material fact about a task outcome, by classifying the terminal state, comparing it against the contract, filtering activity out, and checking that no material fact was lost to compression. Use this skill at a task boundary — when work is complete, partial, blocked, or failed — whenever the user asks what the outcome was or for a summary of what was accomplished, and whenever an execution run ends and its result must be communicated. Reports consequences and evidence, never the execution trajectory.