iterate-lessons-log

Name: iterate-lessons-log
Author: product-on-purpose

486stars64forks

How to install iterate-lessons-log?

product-on-purpose/pm-skills/iterate-lessons-log

$npx -y skills add product-on-purpose/pm-skills --skill iterate-lessons-log

Installs into the current project.

Summary

Creates a structured lessons learned entry for organizational memory. Use after an incident, a completed project, or a significant learning to record knowledge for future teams and initiatives. Distinct from iterate-retrospective, which facilitates the team ceremony; this skill w

Files · 1

View on GitHub

SKILL.md

1	<!-- PM-Skills \| https://github.com/product-on-purpose/pm-skills \| Apache 2.0 -->
2	# Lessons Log
3
4	A lessons log entry captures significant learning from projects, incidents, or experiences in a format that's useful to future teams who weren't there. Unlike retrospectives (which focus on team improvement), lessons logs focus on organizational knowledge that transcends individual teams.patterns, anti-patterns, and hard-won wisdom.
5
6	## When to Use
7
8	- After completing a significant project or initiative
9	- Following a major incident, outage, or failure
10	- When you realize something important that others should know
11	- After discovering a pattern that keeps recurring
12	- When experienced team members leave (capture their knowledge)
13	- During post-mortems to preserve learnings
14
15	## When NOT to Use
16
17	- You are facilitating the team ceremony itself -> use `iterate-retrospective`; this skill banks the durable entry that outlives it
18	- You are deciding whether to change direction based on results -> use `iterate-pivot-decision`
19	- The learning is an experiment readout -> use `measure-experiment-results` first, then bank the transferable lesson here
20	- You are updating stakeholders on what was learned -> use `foundation-stakeholder-update`
21
22	## Instructions
23
24	When asked to create a lessons log entry, follow these steps:
25
26	1. Choose a Descriptive Title
27	Write a title that someone searching for this topic would find. Include keywords that describe the situation and the learning. Avoid generic titles like "Project X lessons."
28
29	2. Provide Context
30	Explain the situation fully enough that someone who wasn't there can understand it. Include the project, timeline, team, and any relevant constraints. Future readers need this context to assess applicability.
31
32	3. Describe What Happened
33	Write a factual account of what occurred. Be specific about actions taken, decisions made, and outcomes observed. Avoid blame.focus on events and systems.
34
35	4. Extract the Lesson
36	Articulate what you learned clearly. The lesson should be actionable.something others can apply. Distinguish between what you observed and your interpretation of why it matters.
37
38	5. Formulate Recommendations
39	Provide specific guidance for future teams facing similar situations. What should they do? What should they avoid? What questions should they ask?
40
41	6. Define Applicability
42	Help readers know when this lesson applies. What situations trigger relevance? What context makes it more or less applicable?
43
44	7. Add Tags for Searchability
45	Include keywords and categories that will help future searchers find this entry. Think about what someone would search for when facing a similar situation.
46
47	## Output Format
48
49	Use the template in `references/TEMPLATE.md` to structure the output. A complete entry fills every template section: Metadata; Summary; Context; What Happened; The Lesson; Recommendations; Applicability; Supporting Evidence; Tags and Categories; and Review and Updates.
50
51	## Quality Checklist
52
53	Before finalizing, verify:
54
55	- [ ] Title is descriptive and searchable
56	- [ ] Context is complete enough for someone who wasn't there
57	- [ ] Lesson is clearly articulated and actionable
58	- [ ] Recommendations are specific, not vague
59	- [ ] Entry stands alone (doesn't require external context)
60	- [ ] Tags enable future discovery
61
62	## Examples
63
64	See `references/EXAMPLE.md` for a completed example.

People who liked this also viewed

6 picks

Type

iterate-lessons-log

486stars64forks

View on GitHub

How to install iterate-lessons-log?

product-on-purpose/pm-skills/iterate-lessons-log

$npx -y skills add product-on-purpose/pm-skills --skill iterate-lessons-log

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	<!-- PM-Skills \| https://github.com/product-on-purpose/pm-skills \| Apache 2.0 -->
2	# Lessons Log
3
4	A lessons log entry captures significant learning from projects, incidents, or experiences in a format that's useful to future teams who weren't there. Unlike retrospectives (which focus on team improvement), lessons logs focus on organizational knowledge that transcends individual teams.patterns, anti-patterns, and hard-won wisdom.
5
6	## When to Use
7
8	- After completing a significant project or initiative
9	- Following a major incident, outage, or failure
10	- When you realize something important that others should know
11	- After discovering a pattern that keeps recurring
12	- When experienced team members leave (capture their knowledge)
13	- During post-mortems to preserve learnings
14
15	## When NOT to Use
16
17	- You are facilitating the team ceremony itself -> use `iterate-retrospective`; this skill banks the durable entry that outlives it
18	- You are deciding whether to change direction based on results -> use `iterate-pivot-decision`
19	- The learning is an experiment readout -> use `measure-experiment-results` first, then bank the transferable lesson here
20	- You are updating stakeholders on what was learned -> use `foundation-stakeholder-update`
21
22	## Instructions
23
24	When asked to create a lessons log entry, follow these steps:
25
26	1. Choose a Descriptive Title
27	Write a title that someone searching for this topic would find. Include keywords that describe the situation and the learning. Avoid generic titles like "Project X lessons."
28
29	2. Provide Context
30	Explain the situation fully enough that someone who wasn't there can understand it. Include the project, timeline, team, and any relevant constraints. Future readers need this context to assess applicability.
31
32	3. Describe What Happened
33	Write a factual account of what occurred. Be specific about actions taken, decisions made, and outcomes observed. Avoid blame.focus on events and systems.
34
35	4. Extract the Lesson
36	Articulate what you learned clearly. The lesson should be actionable.something others can apply. Distinguish between what you observed and your interpretation of why it matters.
37
38	5. Formulate Recommendations
39	Provide specific guidance for future teams facing similar situations. What should they do? What should they avoid? What questions should they ask?
40
41	6. Define Applicability
42	Help readers know when this lesson applies. What situations trigger relevance? What context makes it more or less applicable?
43
44	7. Add Tags for Searchability
45	Include keywords and categories that will help future searchers find this entry. Think about what someone would search for when facing a similar situation.
46
47	## Output Format
48
49	Use the template in `references/TEMPLATE.md` to structure the output. A complete entry fills every template section: Metadata; Summary; Context; What Happened; The Lesson; Recommendations; Applicability; Supporting Evidence; Tags and Categories; and Review and Updates.
50
51	## Quality Checklist
52
53	Before finalizing, verify:
54
55	- [ ] Title is descriptive and searchable
56	- [ ] Context is complete enough for someone who wasn't there
57	- [ ] Lesson is clearly articulated and actionable
58	- [ ] Recommendations are specific, not vague
59	- [ ] Entry stands alone (doesn't require external context)
60	- [ ] Tags enable future discovery
61
62	## Examples
63
64	See `references/EXAMPLE.md` for a completed example.

People who liked this also viewed

6 picks

Type