[feature request] ce-postmortem

Open
#919 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
typescript

Research direction

The issue proposes official support for postmortems but leaves the skill or documentation format undecided. Start by reading the repository’s existing skills and documentation to understand how workflows are defined. Done means proposing and implementing a clear postmortem workflow, including where its documents go and how they support future work; the issue does not identify specific files or tests.

Written by the indexing model from the issue text.

Description

After a few brainstorm->plan->work->compound cycles, there's bound to be bugs and slight errors that are caught. I've found that running postmortems on bug fixes (and committing documents) helps in future work, but I haven't figured out exactly what shape the skill or documentation written should have.

Thoughts on official support for something like that?

Dominant language
TypeScript
Stars
25.6k
Forks
2.1k
Avg merge
3h 57m
Merged PRs (30d)
170

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EveryInc/compound-engineering-plugin

All issues in EveryInc/compound-engineering-plugin

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.