w-retro
Review Completed Work and Improve Next Time
Teams often finish tasks without recording what changed, what evidence was missing, or what should improve. This skill produces a concise, task-specific retrospective with up to three practical next steps.
๋ด ์์ด์ ํธ๋ก ์ค์น
์ด ์์ฒญ์ ์์ด์ ํธ์ ๋ณต์ฌํ์ธ์. ๊ณต์ Skill ํ์ด์ง์ ๋งค๋ํ์คํธ๊ฐ ํฌํจ๋์ด ์์ต๋๋ค.
Review the Skillstore skill "w-retro" from https://skillstore.io/skills/blockmatic-w-retro.md and its manifest at https://skillstore.io/api/skills/blockmatic-w-retro/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.์์ด์ ํธ๋ ๊ณ์ํด์ ๊ณํ์ ํ์ํ๊ณ ๋ณด์ ์ ์ฑ ์์ ์๊ตฌํ๋ ํ์ธ์ ์์ฒญํด์ผ ํฉ๋๋ค.
์์ด์ ํธ๊ฐ ์ฝ๊ธฐ ์ฌ์ด ๋ฆฌ์์ค
AI ์์ด์ ํธ, ํฌ๋กค๋ฌ, ์คํฌ๋ฆฝํธ๊ฐ ์ ์ฒด ํ์ด์ง ๋์ ์ ๋ฆฌ๋ ์ปจํ ์คํธ๋ง ํ์ํ ๋ ์ด ๋งํฌ๋ฅผ ์ฌ์ฉํ์ธ์.
ํ ์คํธํด ๋ณด๊ธฐ
"w-retro" ์ฌ์ฉ ์ค์ ๋๋ค. We needed to add export filtering. The filter shipped and unit tests passed, but no browser test was run.
์์ ๊ฒฐ๊ณผ:
Requested versus shipped: Export filtering was added and unit-tested. Evidence gap: Browser behavior was not checked. Next change: Add one browser test for filter selection and downloaded results.
"w-retro" ์ฌ์ฉ ์ค์ ๋๋ค. The task was to update the onboarding guide. The guide changed, but the examples were not checked against the current interface.
์์ ๊ฒฐ๊ณผ:
- Requested versus shipped: The onboarding guide was updated, but example accuracy was not verified.
- Process gap: The task lacked a user-interface consistency check.
- Next changes: Review examples against the current interface and add a lightweight documentation checklist.
๋ณด์ ๊ฐ์ฌ
์์ The scanned skill is a 12-line, chat-only retrospective checklist with no executable code or detected security patterns. No prompt-injection, data-exfiltration, or business-logic abuse evidence was found in SKILL.md.
์ด ๋ณด๊ณ ์ ๊ณต์ ๋ฐ ์ธ์ฉ
๋ฒ์ ์ด ์ง์ ๋ ํ๊ฐ ๋ณด๊ณ ์, ์ค๋ฆฝ ๋ฐฐ์ง, ์๋ฒ ๋ ์นด๋ ๋ฐ ์ธ์ฉ์ ๊ณต์ ํ์ธ์. Skillstore๋ ๊ทผ๊ฑฐ๋ฅผ ๋ณด๊ณ ํ์ง๋ง ์ด Skill์ ์์ ์ฌ๋ถ๋ฅผ ํ๋จํ์ง ์์ต๋๋ค.
๋ณด๊ณ ์ ๋งํฌ ๋ณต์ฌ
https://skillstore.io/skills/blockmatic-w-retro/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown ๋ฐฐ์ง
[](https://skillstore.io/skills/blockmatic-w-retro?utm_source=security_passport_badge)HTML ๋ฐฐ์ง
<a href="https://skillstore.io/skills/blockmatic-w-retro?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/blockmatic-w-retro/security.svg" alt="Skillstore security assessment" loading="lazy"></a>์๋ฒ ๋ ์นด๋
<iframe src="https://skillstore.io/embed/skills/blockmatic-w-retro.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>ํ์ ์ธ์ฉ (APA ยท BibTeX ยท CFF)
APA ์ธ์ฉ
blockmatic. (2026). w-retro security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/blockmatic-w-retro/audits/1BibTeX ์ธ์ฉ
@techreport{blockmatic-blockmatic-w-retro-2026,
author = {blockmatic},
title = {w-retro security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/blockmatic-w-retro/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "w-retro security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "blockmatic"
date-released: "2026-09-20"
url: "https://skillstore.io/skills/blockmatic-w-retro/audits/1"
identifiers:
- type: other
value: "skillstore:blockmatic-w-retro:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore ์ ์
์ด ์ ์์ ์ด์ ์ฆ๊ฑฐ ์ ๋ขฐ๋: ์ค๊ฐ๋ง๋ค ์ ์๋ ๊ฒ
Close a development task
Review the request, shipped changes, checks, and documentation before closing a coding task.
Improve team delivery
Capture specific process gaps after a sprint item, project milestone, or cross-functional deliverable.
Evaluate an AI-assisted workflow
Compare the requested work with the AI-produced result and record better checks for the next session.
์ด ํ๋กฌํํธ๋ฅผ ์ฌ์ฉํด ๋ณด์ธ์
Review the completed task in this conversation. State what was requested, what shipped, and one improvement for next time.
Run a retrospective on this completed task. Identify skipped checks, unclear requirements, extra scope, and missing documentation. Suggest no more than three specific changes.
Compare the original request, plan, implementation, and validation evidence. Explain the most important differences and recommend up to three changes for the next similar task.
Perform a task-specific retrospective of this AI-assisted delivery. Separate outcome gaps from process gaps, cite the available evidence, and prioritize three changes that would improve the next session.
๋ชจ๋ฒ ์ฌ๋ก
- Run the skill after checks are complete and the delivered result is known.
- Provide the original request, completed work, validation evidence, and relevant constraints.
- Prefer specific recommendations tied to this task over broad process advice.
ํผํ๊ธฐ
- Do not use the retrospective as a substitute for implementing a required fix.
- Do not request generic lessons without sharing task-specific evidence.
- Do not turn a short retrospective into an unfocused list of every possible improvement.
์์ฃผ ๋ฌป๋ ์ง๋ฌธ
When should I use this skill?
What does the skill review?
How many improvements does it suggest?
Can it change files or create commits?
What context produces the best result?
Does it replace a formal incident review?
๊ฐ๋ฐ์ ์ธ๋ถ ์ ๋ณด
์์ฑ์
blockmatic๋ผ์ด์ ์ค
MIT
Skillstore ๋ฆฌ๋น์
r1
๋ฒ์ ์๋ด
์์ฑ์๊ฐ ๋ฒ์ ์ ์ ์ธํ์ง ์์์ต๋๋ค.
๋ฆฌํฌ์งํ ๋ฆฌ
https://github.com/blockmatic/basilic-skills/tree/5fa16493413923e31f1df31f7260224f0f291d9e/skills/w-retro์ฐธ์กฐ
7cd60e5c44d39477abb7a2c00ae0de2cf2a01392
์ ์ง๋ณด์ ์ต์ ์ฑ
2026. 9. 20.
์ฌ์ฉ๋
0 ๋ค์ด๋ก๋ ยท 0 ์กฐํ
ํ์ผ ๊ตฌ์กฐ
๐ SKILL.md