iwe-rules-review
Skill0 starsChanged 27 days agoMITView on GitHub
Weekly review of IWE work culture (element 14 — System Evolution). Runs
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- TserenTserenov/FMT-exocortex-templateedited, first seen Nov 2, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- TserenTserenov/FMT-exocortex-template★ 6411% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-faultSkill
- apply-capturesSkill
- archgateSkill
- artifactorSkill
- audit-docsSkill
- audit-installationSkill
- author-modeSkill
- bottleneck-pickSkill
- check-secretSkill
- consentSkill
- day-closeSkill
- day-openSkill
- decomposeSkill
- diagnoseSkill
- discovery-sessionSkill
- extendSkill
- fpfSkill
- integration-gateSkill
- iwe-bug-reportSkill
- iwe-platform-redteamSkill
- iwe-restoreSkill
- iwe-updateSkill
- keSkill
- kimi-peer-writerSkill
- local-llmSkill
- month-closeSkill
- org-devSkill
- pack-creatorSkill
- pack-newSkill
- peer-conversationSkill
- personal-guide-renderSkill
- personal-guide-startSkill
- platform-bottleneckSkill
- repo-newSkill
- restore-exocortexSkill
- run-protocolSkill
- setup-wakatimeSkill
- skill-creatorSkill
- strategy-sessionSkill
- skill-idSkill
- thinkSkill
- transcribeSkill
- vdvSkill
- verify-hypothesesSkill
- verifySkill
- week-close-pilotSkill
- week-closeSkill
- wp-newSkill
- w-reflectionSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Read PACK-digital-platform/pack/digital-platform/03-methods/DP.M.008-iwe-operating-rules.md → §2 Registry (14 work culture elements).
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
IWE Work Culture Review
Trigger: Week Close (automatic) or manual. Role: R1 Strategist. Input: DP.M.008 (Pack) + weekly data (commits, DayPlans, Quick Close reports). Output: Change proposal → approval → update DP.M.008 + implementations.
Algorithm
1. Load the rules
Read PACK-digital-platform/pack/digital-platform/03-methods/DP.M.008-iwe-operating-rules.md → §2 Registry (14 work culture elements).
2. Four questions (for each rule)
| # | Question | Data source | Action |
| 1 | What did I learn? | Quick Close reports, captures for the week | Record new knowledge |
| 2 | Which rule was an obstacle? | DayPlans, git diff | Rule is unrealistic → simplify or remove |
| 3 | Which rule was missing? | fleeting-notes, memory/ lessons | Recurring pattern with no rule → candidate for formalization |
| 4 | Which rule did I work around? | Quick Close reports | Systematically bypassed → candidate for removal or rework. Dead weight = illusion of control |
3. Generate the report
## IWE Work Culture Review (W{N})
### Health
| Metric | Value | Norm |
|--------|-------|------|
| Violations this week | N | 0-2 |
| Not applied >2 weeks | N rules | 0-1 |
| Candidates for new rule | N | 0-2 |
### Violations
| # | Rule | Count | Reason | Proposal |
|---|------|-------|--------|----------|
### Dead weight
| # | Rule | Last applied | Proposal |
|---|------|-------------|----------|
### Candidates for formalization
| Pattern | Source | Proposed rule |
|---------|--------|---------------|
### Summary
- Changes to DP.M.008: N (remove: ..., add: ..., modify: ...)
- Changes to implementation: N (CLAUDE.md, protocol-*.md, skills/)4. Approval
Present the report → user approves → apply changes to DP.M.008 and implementations.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

