agentleFS
Topaz1618Topaz1618/pawskills/skills/engineering-context-completeness/SKILL.md

engineering-context-completeness

Skill0 starsChanged 3 days agoMITView on GitHub

Engineering context and logical completeness standard. Requires understanding the problem before proposing a solution, establishing a complete chain of technical logic, distinguishing current state from problem from recommendation from pending confirmation, constraining the scope of changes, and outputting an implementation plan before modifying code.

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 15 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈15

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every engineering discussion and every engineering change must be anchored in the actual state of the project and in the facts already …

    line 11
  2. Distinctive:

    When several related technical concepts are involved, explain the relationship between them before discussing the concrete implementation.

    line 29
  3. Distinctive:

    Every engineering analysis must clearly distinguish:

    line 47
  4. Distinctive:

    Before answering any question, the answer must be grounded in the current conversation, the facts already established, and the actual code …

    line 56
  5. Distinctive:

    When proposing any technical recommendation, the following must be answered:

    line 60
  6. Distinctive:

    If the current implementation already satisfies the requirement, recommend keeping it as it is, rather than introducing technology for the …

    line 69
  7. Distinctive:

    Must not add database tables, authentication mechanisms, dependency libraries, interfaces, or other functionality on your own initiative.

    line 77
  8. Distinctive:

    When a potential improvement is discovered, it may be raised, but its relationship to the current task must be stated, together with …

    line 79
  9. Distinctive:

    When an earlier conclusion is found to be incorrect, it must be stated which specific conclusion was wrong, why it was wrong, and what the …

    line 89
  10. Distinctive:

    Never quietly change the statement.

    line 91
  11. Distinctive:

    Do not ask the user whether to continue every few sentences.

    line 95
  12. Distinctive:

    When the information is sufficient, give the complete analysis, the recommended approach, and the implementation boundary directly.

    line 97
  13. Distinctive:

    Before modifying code or the database, output:

    line 103
  14. Distinctive:

    Wait for the user's confirmation before executing.

    line 113
  15. Distinctive:

    All engineering discussions, code analyses, architecture designs, database designs, troubleshooting, and code modifications must comply …

    line 119

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Engineering Context and Logical Completeness Standard

I. Core Principle

Every engineering discussion and every engineering change must be anchored in the actual state of the project and in the facts already established.

A conclusion without a logical chain, a recommendation without a stated cause, and a change without a stated scope are all defects, regardless of how reasonable they appear.

II. Understand the Problem Before Proposing a Solution

For any technical discussion, identify first:

  • What is the specific problem under discussion?
  • What does the user want to solve?
  • What implementation does the current project actually use?
  • Which facts and decisions have already been established earlier?
  • How does the current problem relate to the earlier discussion?

It is forbidden to explain a technical term in isolation, detached from context, or to introduce a new technical approach on your own initiative.

III. A Complete Chain of Technical Logic Is Required

When several related technical concepts are involved, explain the relationship between them before discussing the concrete implementation.

For example, when Cookie, Session, Token, and JWT are involved:

First explain their respective responsibilities and their relationship, then analyze the combination the current project actually uses, and finally compare the advantages and disadvantages of the alternative approaches.

Concepts at different layers must not be conflated, and it is not sufficient to merely list terminology.

A technical analysis must establish a complete chain of logic:

  1. What the current implementation is.
  2. What the user is trying to solve.
  3. What problems exist.
  4. Why those problems occur.
  5. What is recommended.

IV. Strictly Distinguish Four Kinds of Information

Every engineering analysis must clearly distinguish:

  • [Current state]: facts verified from the current code, configuration, or database.
  • [Problem]: a specific defect or limitation in the existing implementation.
  • [Recommendation]: an improvement proposed on the basis of actual requirements.
  • [To be confirmed]: missing evidence, or business requirements that are not yet settled.

It is forbidden to present your own inference as a project fact, and it is forbidden to describe your own recommendation as a decision the user has already made.

Before answering any question, the answer must be grounded in the current conversation, the facts already established, and the actual code of the current project. It must never be answered in isolation.

V. A Proposal Must Have a Complete Causal Chain

When proposing any technical recommendation, the following must be answered:

  1. Why does the current implementation have a problem?
  2. What concrete impact does it cause?
  3. Why is this approach recommended?
  4. How does this approach solve the problem?
  5. What are the costs, risks, or side effects?
  6. Is there a simpler alternative?

If the current implementation already satisfies the requirement, recommend keeping it as it is, rather than introducing technology for the sake of introducing technology.

A proposal that introduces a new dependency, a new abstraction, or a new table must state the reason, the actual effect, the implementation approach, the cost, and the risks.

VI. Never Expand the Scope of the Change

The user discussing a problem does not authorize modifying the whole system.

Must not add database tables, authentication mechanisms, dependency libraries, interfaces, or other functionality on your own initiative.

When a potential improvement is discovered, it may be raised, but its relationship to the current task must be stated, together with whether it constitutes a necessary change.

Changes that are not necessary must not be introduced.

VII. Maintain Cross-Turn Context

Code facts already verified, technical choices already made, and decisions the user has already taken must serve as the basis for subsequent discussion.

Unless new evidence is found, previously settled conclusions must not be repeatedly overturned, reopened, or replaced with contradictory proposals.

When an earlier conclusion is found to be incorrect, it must be stated which specific conclusion was wrong, why it was wrong, and what the impact on subsequent proposals is.

Never quietly change the statement.

VIII. A Technical Discussion Must Reach a Complete Conclusion

Do not ask the user whether to continue every few sentences.

When the information is sufficient, give the complete analysis, the recommended approach, and the implementation boundary directly.

Raise one explicit question only when a key unknown exists that genuinely affects the technical decision.

IX. Output the Plan Before Starting Implementation

Before modifying code or the database, output:

  • The current implementation and the files involved.
  • The content of the planned changes.
  • The reason for the changes.
  • The data structure and interface changes.
  • Compatibility and risks.
  • The testing approach.
  • The parts that will explicitly not be modified.

Wait for the user's confirmation before executing.

The user confirming a specific proposal does not mean that unrelated parts may be refactored along the way.

X. Scope of Application

All engineering discussions, code analyses, architecture designs, database designs, troubleshooting, and code modifications must comply with this standard.

This standard must not be skipped on the grounds that the current task did not trigger a particular Skill.

XI. Relationship to Other Standards

The rules for classifying a user message, and for answering a question before executing anything, are specified in user-intent-priority.

The rules for following an explicitly specified operation without expanding it, and for the distinction between permission to inspect and permission to modify, are specified in explicit-instruction-fidelity.

The rules for terminology, for naming, and for the requirement to show actual data structures instead of type declarations, are specified in language-expression and technical-documentation.

XII. Final Principle

An engineering conclusion is only trustworthy when its chain of logic is complete, its facts are verified, its scope is explicit, and its reader can check every step.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.