[{"data":1,"prerenderedAt":207},["ShallowReactive",2],{"docs-\u002Fdocs\u002Fworkflows\u002Ffeature-specifications":3},{"id":4,"title":5,"body":6,"description":199,"extension":200,"meta":201,"navigation":202,"path":203,"seo":204,"stem":205,"__hash__":206},"docs\u002Fdocs\u002Fworkflows\u002Ffeature-specifications.md","Feature specifications",{"type":7,"value":8,"toc":185},"minimark",[9,13,17,22,25,31,36,39,43,48,51,76,79,83,86,113,117,120,135,138,142,145,149,156,170,174],[10,11,5],"h1",{"id":12},"feature-specifications",[14,15,16],"p",{},"The feature specifications workflow takes a plain-language description of something you want to build and produces a verified, structured specification document with a full task breakdown.",[18,19,21],"h2",{"id":20},"how-to-start-it","How to start it",[14,23,24],{},"Just describe what you want to build:",[26,27,28],"blockquote",{},[14,29,30],{},"\"Write a feature specification for adding Stripe payments to the checkout flow.\"",[26,32,33],{},[14,34,35],{},"\"I need a spec for a background job that syncs orders from the Shopify API every 15 minutes.\"",[14,37,38],{},"Slo recognises the intent and runs the full specification workflow automatically.",[18,40,42],{"id":41},"what-happens","What happens",[44,45,47],"h3",{"id":46},"pre-hook-context-gathering","PRE hook — context gathering",[14,49,50],{},"Before writing anything, Slo reads:",[52,53,54,63,66,73],"ul",{},[55,56,57,58,62],"li",{},"Your ",[59,60,61],"code",{},"CLAUDE.md"," — coding conventions and ground rules",[55,64,65],{},"The relevant code surfaces in your project",[55,67,68,69,72],{},"Your knowledge base (if you have one at ",[59,70,71],{},"~\u002FCode\u002FKnowledgeBase\u002F",")",[55,74,75],{},"Any applicable skill files for the tech stack involved",[14,77,78],{},"This makes sure the spec reflects your actual conventions, not generic advice.",[44,80,82],{"id":81},"spec-writing","Spec writing",[14,84,85],{},"Slo writes the specification as a structured document covering:",[52,87,88,95,101,107],{},[55,89,90,94],{},[91,92,93],"strong",{},"What"," — the user-facing behaviour and acceptance criteria",[55,96,97,100],{},[91,98,99],{},"Why"," — the motivation, constraints, and stakeholders",[55,102,103,106],{},[91,104,105],{},"How"," — the technical approach, broken down by layer (API, domain, UI, tests)",[55,108,109,112],{},[91,110,111],{},"Second-order requirements"," — scale, latency, idempotency, logging, deployment",[44,114,116],{"id":115},"post-hook-verification","POST hook — verification",[14,118,119],{},"After writing, Slo verifies the spec against:",[52,121,122,129,132],{},[55,123,124,125,128],{},"Every applicable ",[59,126,127],{},"build-*.md"," skill for the tech stack",[55,130,131],{},"Your test verification policy",[55,133,134],{},"Completeness — does it cover all the cases it needs to?",[14,136,137],{},"If anything is missing, Slo revises and re-verifies before finalising.",[44,139,141],{"id":140},"task-breakdown","Task breakdown",[14,143,144],{},"Once the spec passes verification, Slo produces a numbered task list, ordered by dependency, ready to hand off to an engineer or to start immediately.",[18,146,148],{"id":147},"output","Output",[14,150,151,152,155],{},"The spec is saved to ",[59,153,154],{},"specifications\u002F\u003Cfeature-name>\u002F"," in your project directory. Each run produces:",[52,157,158,164],{},[55,159,160,163],{},[59,161,162],{},"spec.html"," — the full specification document",[55,165,166,169],{},[59,167,168],{},"tasks.md"," — the numbered task breakdown",[18,171,173],{"id":172},"tips","Tips",[52,175,176,179,182],{},[55,177,178],{},"The more context you give upfront, the better the spec. Mention the tech stack, affected users, and any known constraints.",[55,180,181],{},"If you have existing API documentation or a knowledge base, make sure Slo can see it — it uses those to check for consistency.",[55,183,184],{},"You can ask Slo to revise the spec after reviewing it: \"The spec looks good but the auth section is missing — please add it.\"",{"title":186,"searchDepth":187,"depth":187,"links":188},"",2,[189,190,197,198],{"id":20,"depth":187,"text":21},{"id":41,"depth":187,"text":42,"children":191},[192,194,195,196],{"id":46,"depth":193,"text":47},3,{"id":81,"depth":193,"text":82},{"id":115,"depth":193,"text":116},{"id":140,"depth":193,"text":141},{"id":147,"depth":187,"text":148},{"id":172,"depth":187,"text":173},"How Slo turns a rough feature request into a verified, task-broken specification.","md",{},true,"\u002Fdocs\u002Fworkflows\u002Ffeature-specifications",{"title":5,"description":199},"docs\u002Fworkflows\u002Ffeature-specifications","AG24NG8KHepD8c1jaHpErF0n2jBvwKKScKMJYintewo",1782392848392]