Repository navigation
feat(skills): return a process specification from pipefy-process-design - #850
Open
adriannoes wants to merge 2 commits into
Open
adriannoes wants to merge 2 commits into
adriannoes wants to merge 2 commits into
Conversation
This was referenced Nov 5, 2026
adriannoes
marked this pull request as ready for review
November 5, 2026 16:26
adriannoes
marked this pull request as draft
November 6, 2026 00:53
adriannoes
marked this pull request as ready for review
November 6, 2026 16:38
Signed-off-by: Adrianno Esnarriaga <hey@adrianno.es>
Signed-off-by: Adrianno Esnarriaga <hey@adrianno.es>
adriannoes
force-pushed
the
ad-dev/feat/process-design-specification
branch
from
November 9, 2026 13:19
5d06fa1 to
b79ef7e
Compare
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
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.
#851 and #852 stack on this branch. Merge this PR first.
Summary
pipefy-process-designreturns a specification with 14 fields and writes nothing to Pipefy.advise only,build,build inactive, andpublish. Each webhook, external email, or member invitation needs separate consent.buildstarts automations and AI agents on, except for the five off cases in the specification.aiParamsand writable event values, without response-only fields.Accepted limits
The diff exceeds the 300-line guideline. The two new references contain the specification contract and selection rules. Consider reviewing them separately.
Until #852 merges, the domain skills retain their earlier consent wording and can ask about AI again after specification approval.
The five off cases cover an inactive request, an unconfirmed assumption, and a missing phase connection. They also cover a pre-existing pipe with matching cards or a time rule in a pipe with cards. The builder reads the two card cases again before activation. The other cases wait for the required consent or connection.
Test plan
dev: no conflict.Docs / skills
docs/parity.mdupdated when MCP ↔ CLI coverage changed (no coverage change)plugins/pipefy/skills/updated in this PR (or a paired PR)Legal / contributions
git commit -s)COMPLIANCE.mdwhen applicable (none added)