ap

Solid

Implement <SPEC>, keeping a running apply-notes HTML file of out-of-spec decisions and tradeoffs.

Code & Development 37 stars 10 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
53
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
35
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

Implement <SPEC>; and while you do, keep a running apply-notes.html file with decisions you had to make that weren't in the spec, things you had to change, tradeoffs you had to make, or anything else I should know. It is not a work log — routine progress like tests passing or builds going green doesn't belong in it. Keep the file at `${TMPDIR%/}/apply-notes-<feature-name>.html`, never inside the repo, one file per requirement: when a round continues the same task, append to the existing file under a new round heading rather than starting a fresh one; only a new requirement gets a new file. Always update it with the Edit tool (Write only when first creating it), never through shell redirection.

Details

Author
Surething-io
Repository
Surething-io/cockpit
Created
7 months ago
Last Updated
3 days ago
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category