[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71PAM19Z1XTV9NPCFSE2MY8":3,"skill-same:01M71PAM19Z1XTV9NPCFSE2MY8":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":50,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect",null,"Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"workflow architect","architect","workflow","systems","https","operations","recovery","github","monomind","leadership","state","architecture","code","workflows","map","for","planning","branch","user journeys","trees","2026-11-10 13:02:02",false,"---\nname: workflow-architect\ndescription: \"Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.\"\ntags: [\"leadership\",\"operations\",\"architecture\",\"planning\"]\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\n---\n# Workflow Architect — Best Practices\n\n## Focus\nMaps complete workflow trees for systems, user journeys, and agent interactions — happy paths, every branch, failure modes, recovery paths, and handoff contracts — before implementation starts.\n\n## Best practices\n- Discover workflows before designing them: read every route, worker, migration, and infra config — most workflows are implied by code, never announced.\n- Design branches, not just the happy path: every step needs its validation failures, timeouts, transient\u002Fpermanent failures, partial failures, and concurrent conflicts covered.\n- Define explicit handoff contracts at every system boundary — payload shape, success\u002Ffailure response, timeout value, and the recovery action on failure.\n- Specify observable state at every step: what the customer sees, what the operator sees, what's in the database, what's in the logs.\n- Build a cleanup inventory for every resource a workflow creates — every created resource needs a corresponding destroy path on failure.\n- Verify specs against actual code, not stated intent — code and description diverge constantly; find and surface the divergence.\n- Track every unverifiable assumption explicitly in the spec — an untracked assumption is a future bug.\n\n## Common pitfalls\n- Specifying only the success case and leaving failure\u002Ftimeout\u002Fpartial-failure branches implicit or unwritten.\n- Making implementation decisions instead of specifying required behavior — that's the implementer's job, not the spec's.\n- Leaving a handoff's failure response or timeout undefined, so downstream code guesses.\n- Letting the spec drift silently from the code after either one changes.\n\n## Tools & techniques\n- Structured workflow-tree spec format: Trigger -> Steps (with timeout\u002Fsuccess\u002Ffailure) -> Cleanup Inventory -> State Transitions -> Test Cases.\n- Discovery pass over routes, workers, migrations, and IaC before writing any spec.\n- Derive one test case per branch in the tree — an unspecced branch is an untested branch.\n- Cross-check every spec with a reality pass against the actual implementation before marking it approved.\n","# Workflow Architect — Best Practices\n\n## Focus\nMaps complete workflow trees for systems, user journeys, and agent interactions — happy paths, every branch, failure modes, recovery paths, and handoff contracts — before implementation starts.\n\n## Best practices\n- Discover workflows before designing them: read every route, worker, migration, and infra config — most workflows are implied by code, never announced.\n- Design branches, not just the happy path: every step needs its validation failures, timeouts, transient\u002Fpermanent failures, partial failures, and concurrent conflicts covered.\n- Define explicit handoff contracts at every system boundary — payload shape, success\u002Ffailure response, timeout value, and the recovery action on failure.\n- Specify observable state at every step: what the customer sees, what the operator sees, what's in the database, what's in the logs.\n- Build a cleanup inventory for every resource a workflow creates — every created resource needs a corresponding destroy path on failure.\n- Verify specs against actual code, not stated intent — code and description diverge constantly; find and surface the divergence.\n- Track every unverifiable assumption explicitly in the spec — an untracked assumption is a future bug.\n\n## Common pitfalls\n- Specifying only the success case and leaving failure\u002Ftimeout\u002Fpartial-failure branches implicit or unwritten.\n- Making implementation decisions instead of specifying required behavior — that's the implementer's job, not the spec's.\n- Leaving a handoff's failure response or timeout undefined, so downstream code guesses.\n- Letting the spec drift silently from the code after either one changes.\n\n## Tools & techniques\n- Structured workflow-tree spec format: Trigger -> Steps (with timeout\u002Fsuccess\u002Ffailure) -> Cleanup Inventory -> State Transitions -> Test Cases.\n- Discovery pass over routes, workers, migrations, and IaC before writing any spec.\n- Derive one test case per branch in the tree — an unspecced branch is an untested branch.\n- Cross-check every spec with a reality pass against the actual implementation before marking it approved.\n",{"name":5,"tags":48,"tools":49,"source":50,"license":14,"description":7},[32,28,34,39],[],"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect",2,"https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add monoes\u002Fmonomind --skill workflow-architect",{"tool":65,"command":66},"bunx","bunx skills add monoes\u002Fmonomind --skill workflow-architect",{"tool":68,"command":69},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill workflow-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",true,[],[74,100,134,161,183,207],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":43},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[81,82,83,84,85,86,87,88,89,90,91,92,31,93,94,95,96,97,98,99],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","knowledge","impact","query","snark","review","security review","stark","zettelkasten","cryptography","security","org","blockchain",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":104,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":116,"publishedAt":43},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[108,111],{"categoryNo":109,"categoryName":110,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[117,118,119,85,120,121,122,123,90,35,124,125,126,127,128,129,130,131,132,133],"writing","writing plans","plans","superpowers","implementation plan","when","you","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":138,"sourceHtmlUrl":139,"categories":140,"keywords":144,"publishedAt":43},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[141],{"categoryNo":142,"categoryName":143,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000031","产品经理",[127,145,146,147,148,88,149,122,150,151,152,126,153,154,155,156,157,158,159,160],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":165,"sourceHtmlUrl":166,"categories":167,"keywords":171,"publishedAt":43},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[168],{"categoryNo":169,"categoryName":170,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000033","数据分析师",[90,127,172,173,38,174,88,159,122,175,176,177,178,152,30,179,27,180,181,182],"write query","postgres","snowflake","best practices","natural-language","with","multi","sql","syntax","plugins","data",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":193,"publishedAt":43},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[189,192],{"categoryNo":190,"categoryName":191,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[194,195,25,196,38,197,198,199,200,89,201,202,203,90,31,30,204,205,206,27],"Workflow Automation","automation","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":211,"categories":212,"keywords":213,"publishedAt":43},"01M71PAHFJHG641X0RR432KB3G","worker-specialist","Org role guidance for a worker specialist: execute one assigned, well-scoped task with precision and report status honestly at real milestones. Covers confirming done-criteria first, surfacing blockers immediately and sharing intermediate results with peers.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworker-specialist\u002FSKILL.md",[],[214,215,216,38,217,218,219,220,221,222,177,223,31,30,224,28,225,226,227,27],"worker","worker specialist","specialist","scoped","milestones","done","one","coordination","task","first","results","report status","sharing","at"]