Files
BMAD-METHOD/samples/sample-custom-modules/sample-unitary-module/workflows/wassup/workflow.md
Alex Verkhovsky 19df17b261 feat: add documentation website with Docusaurus build pipeline (#1177)
* feat: add documentation website with Docusaurus build pipeline

* feat(docs): add AI discovery meta tags for llms.txt files

- Add global headTags with ai-terms, llms, llms-full meta tags
- Update landing page link to clarify AI context purpose

* fix(docs): restore accidentally deleted faq.md and glossary.md

Files were removed in 12dd97fe during path restructuring.

* fix(docs): update broken project-readme links to GitHub URL

* feat(schema): add compound trigger format validation
2025-12-23 23:01:36 +08:00

1.1 KiB

name, description, web_bundle
name description web_bundle
wassup Will check everything that is local and not committed and tell me about what has been done so far that has not been committed. true

Wassup Workflow

Goal: To think about all local changes and tell me what we have done but not yet committed so far.

Critical Rules (NO EXCEPTIONS)

  • 🛑 NEVER read partial unchanged files and assume you know all the details
  • 📖 ALWAYS read entire files with uncommited changes to understand the full scope.
  • 🚫 NEVER assume you know what changed just by looking at a file name

INITIALIZATION SEQUENCE

    1. Find all uncommitted changed files
    1. Read EVERY file fully, and diff what changed to build a comprehensive picture of the change set so you know wassup
    1. If you need more context read other files as needed.
    1. Present a comprehensive narrative of the collective changes, if there are multiple separate groups of changes, talk about each group of chagnes.
    1. Ask the user at least 2-3 clarifying questions to add further context.
    1. Suggest a commit message and offer to commit the changes thus far.