A clear plan makes big features easier to build. Start by writing a PRODUCT.md file that describes what users will see. Then write a TECH.md file for the technical approach when needed. Keep both files updated as you code. This keeps everyone on the same page and reduces mistakes.
Use this skill when starting a significant feature or when working with an AI agent. The specs live in a folder called specs/ with the ticket number. They are checked into source control so others can review them.
Global
mkdir -p ~/.claude/skills/spec-driven-implementationProject
mkdir -p .claude/skills/spec-driven-implementationSource Repository
Lark Drivelarksuite/cli
Organize Lark cloud files import export manage permissions and versions
Lark Eventlarksuite/cli
Stream Lark events in real time with simple CLI commands
Lark Workflow Meeting Summarylarksuite/cli
Turn your Lark meeting notes into organized weekly summaries with ease
Lark Approvallarksuite/cli
Easily manage Lark approval instances and tasks from your command line
Executing Plansobra/superpowers
Load a plan review critically then execute each task with verifications
Subagent Driven Developmentobra/superpowers
Execute plans with fresh subagents per task and thorough reviews for fast iteration
Churn Preventioncoreyhaines31/marketingskills
Reduce customer churn with smart cancel flows and failed payment recovery
Baoyu Danger X To Markdownjimliu/baoyu-skills
Save X tweets and articles as markdown files with YAML front matter