requirement-ledger-workflow
De la autor
FIRST RESPONSE CONTRACT for one selected Chinese project: a takeover's first visible text, including any required Skill-use announcement, must begin exactly `可以接管。`; a progress request's complete pre-tool acknowledgement must be exactly `可以汇报。`. Treat a report from the current CONTEXT checkpoint as a bounded status answer, not a new audit or Worker task. Use when the user says Jarvis/贾维斯, “接管这个项目”, “汇报一下项目进度”, or asks Codex to manage, review, diagnose, accept, or hand off one selected task, Agent Skill, Git project, or explicit export. Select a direct answer, an explained answer, or the full Jarvis project report according to what the user asked; do not force every reply into one dashboard. Also use for bounded daily/weekly reviews and explicit-source verification. Do not discover all history, install software, expose private evidence, or treat analysis as authorization to edit or publish.
Instalare
npx skills add adand-91/gpt-6-astra-skill --skill requirement-ledger-workflow -a claude-code
Se instalează în .claude/skills/requirement-ledger-workflow/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
Vrei ca agentul să-ți propună skill-uri în timp ce scrii? Vezi cum folosești skill-urile din IDE.
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 81
aiqbench calculează scorul de încredere din semnale publice. Nu este un audit de securitate, așa că citește un skill înainte să-l instalezi.
Skill-uri similare
Cele mai apropiate de acesta prin ce fac și când sunt folosite.
- requirement-ledgeradand-91/gpt-6-astra-skillRun the advanced, evidence-bound Requirement Ledger CLI workflow from an explicit target, window, scope, and files; create private evidence, candidates, exact report bindings, and a read-only handoff check. Use for reproducible review/continuity, not the Codex host-selected quick audit, history discovery, autonomous edits, or publication.Planificare★ 124
- zhangyi-takeoveraph199686/zhangyi-studio张翼接管：接手已在开发中、方向已定的项目，跳过立项——只读核验现状、免立项确认、深度建立框架与目录理解、经显式授权后整理目录、任务编排与接续台账（ledger）。Use when the user has an existing in-progress game project (possibly built with another AI or a previous developer), wants to skip kickoff, and needs takeover, project management, task orchestration, or continuation development. 用户带着做了一半的游戏工程、想跳过立项、需要接管/项目管理/统筹/排期/任务拆解/接续开发时使用。Productivitate★ 119
- jiaojieJordanwei1/jiaojie-skillCreate or receive human-first AI task handoffs across chats, models, devices, and languages. Use when the user asks to hand off, export context, resume from a handoff, switch sessions while preserving work, says "交接一下", "接收交接", or supplies handoff.md, handoff.zip, handoff-audit.zip, an LCH Bundle/T0 package, OCH Snapshot, or LTM Packet. Default to one readable handoff.md; upgrade to handoff.zip only when required files must travel, and to handoff-audit.zip only for formal audit, cross-organization delivery, or proof. Preserve current intent, stop point, next action, decisions, constraints, rejected and failed paths, answered questions, materials, omissions, and revalidation needs. Do not use for generic summaries, memory lookup, hidden reasoning, completed trivial chats, or after the user declines.Productivitate★ 90
- upstream-firstmgifford/accessibility-skillsLoad this skill before implementing a fix for a barrier that may originate in a shared component, design system, renderer, or external dependency rather than this project's own code. Decide whether the responsible fix is local, an existing installed capability, or an upstream contribution before writing a workaround. Absolutely always record any temporary local divergence with an owner and removal condition. Under no circumstances open, comment on, or submit anything in an external project without explicit human approval.Design★ 57
- old-coderAmazingAng/old-coderEvidence-first development — surround the implementation with an executable spec and a gauntlet of constraints (tests, types, coverage, mutation) so line-by-line review becomes optional. Use when the user explicitly asks for high-assurance or evidence-first work ("reliable", "TDD", "prove it works", "I won't read the code"), or when the change touches high-stakes domains (money, auth, data loss, concurrency, public API). For routine changes where the user just wants normal tests, write good tests directly instead of invoking this loop.Testare★ 753
- contract-firstqshanx/docs-governance也适用于同一进程内存在明确消费者、提供者和公共接口且有漂移风险的业务模块；按实际边界验证公开签名与行为，无网络边界时不要求序列化证据。 分前端/后端（或多个服务）多端开发的项目，用 CONTRACT.md 指向的唯一机器契约，各端只照它各做各的，防止字段漂移导致集成时白屏。支持单会话多 agent 和多终端各自跑两种模式。只要项目有前后端/多服务、接口字段老对不上、各端联调卡住、某端改了字段忘了通知别人、或前端为渲染一个页面要调一堆接口拼数据，就用这个 skill，哪怕用户没明说"契约"。这套方法论的学名是消费者驱动契约（Consumer-Driven Contracts, CDC）/ 契约测试。中文触发：契约式开发、接口契约、前后端协作、多终端协作、防字段漂移、接口对不上、联调、API 契约、字段命名不一致、集成白屏、唯一真相源、契约测试、CDC。English triggers: contract-first development, consumer-driven contracts, contract testing, API contract, frontend backend collaboration, multi-terminal, prevent field drift, provider verification.Juridic★ 253
Note și recenzii
—
nicio recenzie
Ai încercat acest skill? Notează-l ca să-i ajuți pe alții. Autentifică-te
Discuție
Intră în discuție. Autentifică-te