chore(docs, rfd): Implement the JP RFD process and tooling#397
Merged
chore(docs, rfd): Implement the JP RFD process and tooling#397
Conversation
Introduce the Request for Discussion (RFD) process to formalize design proposals and architectural decisions. This change adds the initial set of process documents, templates, and automation to manage the lifecycle of design documents from draft to implementation. The process is built around a Git-based workflow where proposals are submitted as markdown files in `docs/rfd/`, reviewed via pull requests, and tracked through a defined set of statuses. New documentation: - `001-jp-rfd-process.md`: Core process definition and lifecycle. - `002-using-llms.md`: Guidelines for responsible LLM usage. - `003-jp-assisted-rfds.md`: Design for JP-assisted RFD writing. Automation and Tooling: - Added `just rfd-draft` to create new proposals from templates. - Added `just rfd-supersede` to manage document relationships. - Introduced the `rfd` skill for JP to act as a drafting partner. The `rfd` skill enables JP to assist contributors by suggesting structure, researching codebase context, and proposing targeted edits while maintaining the principle of human authorship and responsibility. Signed-off-by: Jean Mertz <git@jeanmertz.com>
Signed-off-by: Jean Mertz <git@jeanmertz.com>
Signed-off-by: Jean Mertz <git@jeanmertz.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduce the Request for Discussion (RFD) process to formalize design proposals and architectural decisions. This change adds the initial set of process documents, templates, and automation to manage the lifecycle of design documents from draft to implementation.
The process is built around a Git-based workflow where proposals are submitted as markdown files in
docs/rfd/, reviewed via pull requests, and tracked through a defined set of statuses.New documentation:
001-jp-rfd-process.md: Core process definition and lifecycle.002-using-llms.md: Guidelines for responsible LLM usage.003-jp-assisted-rfds.md: Design for JP-assisted RFD writing.Automation and Tooling:
just rfd-draftto create new proposals from templates.just rfd-supersedeto manage document relationships.rfdskill for JP to act as a drafting partner.The
rfdskill enables JP to assist contributors by suggesting structure, researching codebase context, and proposing targeted edits while maintaining the principle of human authorship and responsibility.