[{"data":1,"prerenderedAt":386},["ShallowReactive",2],{"docs-sections":3,"docs-page-\u002Fdocs\u002Fskill-pdd-map":124},[4,9,13,17,21,25,30,34,38,42,46,50,54,58,62,66,71,75,79,83,88,92,96,100,104,108,112,116,120],{"path":5,"title":6,"description":7,"group":8},"\u002Fdocs","Introduction","pdd-kit brings Product-Driven Development to coding agents through a Git-tracked Product Model and an automatic verification loop.","Get started",{"path":10,"title":11,"description":12,"group":8},"\u002Fdocs\u002Finstallation","Installation","Install the pdd-kit skills into your coding agent at project or global scope.",{"path":14,"title":15,"description":16,"group":8},"\u002Fdocs\u002Ffrom-your-repo","From your repo","Map what an existing repository already does into a Product Model, review it, then check the code against it.",{"path":18,"title":19,"description":20,"group":8},"\u002Fdocs\u002Ffrom-an-idea","From an idea","Decide what a new product does, approve its Product Model, then ask your agent to implement it while verify checks each part.",{"path":22,"title":23,"description":24,"group":8},"\u002Fdocs\u002Ffrom-a-blueprint","From a Blueprint","Pull a reviewed Product Model for a common kind of product instead of starting blank, adapt it if needed, then ask your agent to implement it.",{"path":26,"title":27,"description":28,"group":29},"\u002Fdocs\u002Fproduct-model","Model overview","The Product Model in five minutes (what the product-model\u002F folder holds, what each resource type is for, and how to tell them apart).","Product Model",{"path":31,"title":32,"description":33,"group":29},"\u002Fdocs\u002Fproduct","Product","The one product a Product Model describes (its name, its promise, the languages it is delivered in, its known boundaries, and what it needs to be published as a Blueprint).",{"path":35,"title":36,"description":37,"group":29},"\u002Fdocs\u002Fentities","Entities","The things your product keeps or reasons about (orders, products, settings) and the people and systems that act on it, with what it knows about each and the States it moves through.",{"path":39,"title":40,"description":41,"group":29},"\u002Fdocs\u002Finterfaces","Interfaces","The web apps, mobile apps, CLIs, APIs and webhooks through which people and systems reach your product, the parts inside them, and the places where facts and abilities are met.",{"path":43,"title":44,"description":45,"group":29},"\u002Fdocs\u002Fdomains","Domains","Optional subject areas, such as ordering or billing, that follow the Product's own sections and group its Capabilities and Entities without owning them.",{"path":47,"title":48,"description":49,"group":29},"\u002Fdocs\u002Fcapabilities","Capabilities","The things your product lets someone do, where each is offered, and the Capability Scenarios that show each one working.",{"path":51,"title":52,"description":53,"group":29},"\u002Fdocs\u002Fjourneys","Journeys","Goals where your product carries a person from one Capability into the next, and the Journey Scenarios that walk each path.",{"path":55,"title":56,"description":57,"group":29},"\u002Fdocs\u002Fbusiness-rules","Business Rules","What must always hold in your product, and who may do what (constraints, derivations and permissions), each stated once with everything it applies to.",{"path":59,"title":60,"description":61,"group":29},"\u002Fdocs\u002Fvariations","Variations","Feature flags, settings, plan tiers, A\u002FB tests and API versions, when your product works in more than one supported way and something decides which way applies.",{"path":63,"title":64,"description":65,"group":29},"\u002Fdocs\u002Freferences","References","Point any resource at material kept outside the model (code, a PRD, a design, research), saying what it is and why it is attached.",{"path":67,"title":68,"description":69,"group":70},"\u002Fdocs\u002Fskills","Skills overview","Three self-contained skills cover adoption, intended product change, and automatic verification-to-resolution.","Skills",{"path":72,"title":73,"description":74,"group":70},"\u002Fdocs\u002Fskill-pdd-map","map","Create or expand a Product Model from the code you already have, without running it.",{"path":76,"title":77,"description":78,"group":70},"\u002Fdocs\u002Fskill-pdd-ideate","ideate","Explore or define intended behavior, then write only the exact Product Model change you approve.",{"path":80,"title":81,"description":82,"group":70},"\u002Fdocs\u002Fskill-pdd-verify","verify","Implement the Product Model in code, in phases, or check that the model and the code agree, and resolve every gap you approve until they do or something blocks.",{"path":84,"title":85,"description":86,"group":87},"\u002Fdocs\u002Fcli","CLI overview","Install skills, lint and view a Product Model locally, and move Blueprints between repositories with the pdd-kit CLI.","CLI",{"path":89,"title":90,"description":91,"group":87},"\u002Fdocs\u002Fcli-install","install","Install the bundled pdd-kit agent skills safely for selected AI harnesses and scopes.",{"path":93,"title":94,"description":95,"group":87},"\u002Fdocs\u002Fcli-update","update","Refresh only pdd-kit-managed skill installations in project or global scope.",{"path":97,"title":98,"description":99,"group":87},"\u002Fdocs\u002Fcli-lint","lint","Check that a Product Model is structurally sound (files, relationships, Steps, Rules and References) without claiming it matches the code.",{"path":101,"title":102,"description":103,"group":87},"\u002Fdocs\u002Fcli-view","view","Open a Product Model as a private local report, from your checkout or from a GitHub repository.",{"path":105,"title":106,"description":107,"group":87},"\u002Fdocs\u002Fcli-export","blueprint export","Compile a Product Model into a portable Product Report that can move safely between repositories.",{"path":109,"title":110,"description":111,"group":87},"\u002Fdocs\u002Fcli-open","blueprint open","Expand a local Product Report into a canonical Product Model.",{"path":113,"title":114,"description":115,"group":87},"\u002Fdocs\u002Fcli-list","blueprint list","List the published Blueprints you can pull.",{"path":117,"title":118,"description":119,"group":87},"\u002Fdocs\u002Fcli-pull","blueprint pull","Pull a published Blueprint into the current directory.",{"path":121,"title":122,"description":123,"group":87},"\u002Fdocs\u002Fcli-contribute","blueprint contribute","Open a pull request proposing your Product Model as a Blueprint.",{"id":125,"title":73,"body":126,"description":74,"extension":378,"group":70,"meta":379,"navigation":381,"order":382,"path":72,"seo":383,"stem":384,"__hash__":385},"docs\u002Fdocs\u002Fskill-pdd-map.md",{"type":127,"value":128,"toc":372},"minimark",[129,136,143,154,164,167,172,223,227,230,317,320,333,343,347],[130,131,133],"h1",{"id":132},"pdd-map",[134,135,132],"code",{},[137,138,139],"p",{},[140,141,142],"strong",{},"Map reads your repository and writes a Product Model of what the product\nalready does.",[137,144,145,146,153],{},"Use it once, when you adopt pdd-kit in a repository that has code, and\nagain only for an area the model doesn't cover yet or that you no longer trust.\nIt is not a daily step: to check that the model is still current, use\n",[147,148,150],"a",{"href":149},".\u002Fskill-pdd-verify",[134,151,152],{},"pdd-verify",".",[155,156,162],"pre",{"className":157,"code":159,"language":160,"meta":161},[158],"language-text","\u002Fpdd-map\n\u002Fpdd-map billing\n","text","",[134,163,159],{"__ignoreMap":161},[137,165,166],{},"The first maps the whole repository; the second maps one area and what it\nneeds.",[168,169,171],"h2",{"id":170},"what-you-get","What you get",[173,174,175,191,197,211,217],"ol",{},[176,177,178,181,182,185,186,190],"li",{},[140,179,180],{},"Numbered questions, each with a recommendation."," The code says what\nhappens, not what the product means, so map asks what inspection can't\nsettle: which surfaces are supported ",[147,183,40],{"href":184},".\u002Finterfaces",", whether a\nfamily of things is one ",[147,187,189],{"href":188},".\u002Fentities","Entity"," or several, where a Scenario\nends and an edge case begins, and the product's own name for each thing. It\nasks in rounds and waits for your answers.",[176,192,193,196],{},[140,194,195],{},"The proposed change."," Every resource it would add, change or remove, what\nit left unmapped, and what it couldn't establish, before anything is written.",[176,198,199,202,203,206,207,210],{},[140,200,201],{},"Files written after you approve",", only inside ",[134,204,205],{},"product-model\u002F",". A first\nrun creates the whole folder, including the model's README\n(",[134,208,209],{},"product-model\u002FREADME.md",").",[176,212,213,216],{},[140,214,215],{},"Lint",", fixed until clean.",[176,218,219,222],{},[140,220,221],{},"A report",": what is mapped, what is not, the limitations, and the lint\nresult.",[168,224,226],{"id":225},"how-it-reads-the-code","How it reads the code",[137,228,229],{},"Map starts at the entry points (routes, commands, handlers) and follows each\none through to what it stores and what the person sees. Tests and docs are\nleads; it confirms every claim in the implementation. Then it sweeps four times:",[231,232,233,249],"table",{},[234,235,236],"thead",{},[237,238,239,243,246],"tr",{},[240,241,242],"th",{},"Sweep",[240,244,245],{},"Looks for",[240,247,248],{},"Becomes",[250,251,252,267,283,302],"tbody",{},[237,253,254,258,261],{},[255,256,257],"td",{},"Verbs",[255,259,260],{},"What people and systems can do",[255,262,263,266],{},[147,264,48],{"href":265},".\u002Fcapabilities",", each with Scenarios for its cases",[237,268,269,272,275],{},[255,270,271],{},"Nouns",[255,273,274],{},"Each thing the product keeps",[255,276,277,278,282],{},"Its States, the Steps that move it between them, and the ",[147,279,281],{"href":280},".\u002Finterfaces#screens","Screens"," that show it",[237,284,285,288,291],{},[255,286,287],{},"Permissions",[255,289,290],{},"Every authorization check: a role, an owner, a threshold",[255,292,293,294,298,299],{},"A grant on a ",[147,295,297],{"href":296},".\u002Fbusiness-rules","Business Rule","; an operation refused to everyone is ",[134,300,301],{},"permits: []",[237,303,304,307,310],{},[255,305,306],{},"Hand-offs",[255,308,309],{},"Places where the product carries a person from one Capability into the next",[255,311,312,313],{},"A ",[147,314,316],{"href":315},".\u002Fjourneys","Journey",[137,318,319],{},"A state nothing moves a thing into, or a thing nothing changes, becomes a\nquestion for you, never a guess.",[137,321,322,323,327,328,332],{},"Flags, settings, plans and A\u002FB tests are classified by\n",[147,324,326],{"href":325},".\u002Fvariations#what-selects-decides-it","What selects",": a\n",[147,329,331],{"href":330},".\u002Fvariations","Variation"," only when they switch between complete supported\nforms; otherwise a condition, a separate Scenario, or a condition on who may.",[137,334,335,336,339,340,153],{},"Map attaches what it actually read as ",[147,337,64],{"href":338},".\u002Freferences"," (the code\nit traced, and any PRD or spec that states the behavior) as a record of where a\nclaim came from, not proof. In a repository using a spec-driven tool, it records\nthose folders in ",[134,341,342],{},"config.yaml",[168,344,346],{"id":345},"related","Related",[348,349,350,359,366],"ul",{},[176,351,352,358],{},[147,353,355],{"href":354},".\u002Fskill-pdd-ideate",[134,356,357],{},"pdd-ideate",": decide what should\nchange next.",[176,360,361,365],{},[147,362,363],{"href":149},[134,364,152],{},": check the model and\ncode still agree.",[176,367,368],{},[147,369,371],{"href":370},".\u002Ffrom-your-repo","Start from your repository",{"title":161,"searchDepth":373,"depth":373,"links":374},2,[375,376,377],{"id":170,"depth":373,"text":171},{"id":225,"depth":373,"text":226},{"id":345,"depth":373,"text":346},"md",{"section":380},"open-source",true,17,{"title":73,"description":74},"docs\u002Fskill-pdd-map","UltqmRw6nRxX6oIsZ0E8QUdpwcz-FDDfxEupbRj6NSI",1791840533778]