Skip to content

docs: add RAG failure analysis guide (WFGY 16-problem map)#816

Closed
onestardao wants to merge 6 commits intogithub:stagedfrom
onestardao:staged
Closed

docs: add RAG failure analysis guide (WFGY 16-problem map)#816
onestardao wants to merge 6 commits intogithub:stagedfrom
onestardao:staged

Conversation

@onestardao
Copy link

Closes #719

Pull Request Checklist

  • I have read and followed the CONTRIBUTING.md guidelines.
  • My contribution adds a new instruction, prompt, agent, skill, or workflow file in the correct directory.
  • The file follows the required naming convention.
  • The content is clearly structured and follows the example format.
  • I have tested my instructions, prompt, agent, skill, or workflow with GitHub Copilot.
  • I have run npm start and verified that README.md is up to date.

Description

This PR adds a new instruction file:

instructions/wfgy-core-reasoning-os.instructions.md

It provides a plain-text reasoning core (WFGY Core 2.0) designed to be used as a custom GitHub Copilot instruction.

The goal is to offer a minimal, infrastructure-free reasoning layer that improves multi-step reasoning stability for tasks such as:

  • debugging and refactoring
  • architectural reasoning
  • structured analysis
  • complex pipeline design

The file includes:

  • A drop-in system prompt block
  • A short self-test section for quick validation
  • Clear structure and usage guidance

This contribution was discussed in:
#719 (comment)

Happy to adjust formatting, naming, or structure if needed.


Type of Contribution

  • New instruction file.
  • New prompt file.
  • New agent file.
  • New plugin.
  • New skill file.
  • New agentic workflow.
  • Update to existing instruction, prompt, agent, plugin, skill, or workflow.
  • Other (please specify):

Additional Notes

This instruction is intentionally lightweight and does not introduce any external dependencies or workflow changes.
It is designed to be purely text-based and compatible with standard GitHub Copilot custom instruction usage.


By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.


copy everything in this block into your system / pre-prompt / instructions:

```text
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why isn't everything after this just the instructions file? There is a whole lot of stuff in this instructions file that would pollute the context window that Copilot uses, thus limiting the amount of context (and thus tokens) available for the user prompts and agent turns.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the feedback! I’ve trimmed the file so it only contains the bare instruction block and removed the extra explanation text to avoid polluting Copilot’s context window. Let me know if you’d like it to be even more minimal.

Copy link
Contributor

@aaronpowell aaronpowell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to be honest in that I still really don't understand this in context of Copilot instructions.

The point of an instructions file is that it is something applied to the context of every Copilot request (or scoped if you use applyTo), and I'm not seeing when this would apply.

Firstly, the file tells you that you then need to copy part of it to another file, which is not what an instructions file is for, an instructions file is something you would include without needing to perform an additional step.

Second, I don't understand what the block you're meant to copy in will do. Granted, I'm not a data scientist or AI researcher, but reading through it really don't make any sense to me so I don't know why I would include this in a project.

I understand that there's a repo out there that describes what WFGY is, but looking at this, I'm unsure that it fits into the objectives of this repo.

@onestardao
Copy link
Author

Thanks for the review and clarification.

I understand the mismatch now, and I agree this is probably not the right fit for this repo as an instructions file.

Rather than keep iterating on the current approach, I'll close this PR here. Thanks again for the time and feedback.

@onestardao onestardao closed this Feb 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants