structured-dev结构化开发流水线:Research → Plan → Annotate → Implement。 基于 Boris Tane (Cloudflare) 的 Claude Code 工作流,确保 AI 在架构审查通过前不写一行代码。 触发词:"结构化开发", "structured dev", "走流水线", "R...
Install via ClawdBot CLI:
clawdbot install lskun/structured-devGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Mar 21, 2026
A financial services company needs to add a new payment gateway to their 10-year-old monolithic banking platform. The structured dev pipeline ensures thorough research of existing transaction flows and dependencies before implementation, preventing system-wide failures.
A SaaS company wants to add webhook functionality to their CRM platform. The annotate loop allows product managers to specify exact payload structures and rate limiting requirements before developers write any code, ensuring API consistency.
An online retailer needs to implement a new inventory management feature across their web and mobile apps. The research phase identifies all existing inventory modules, while the todo list breaks implementation into manageable cross-platform tasks.
A hospital management system requires HIPAA-compliant audit logging. The structured approach ensures all data access points are researched and documented before implementation, with multiple annotation rounds for compliance officer review.
A tech startup building their first product uses the pipeline to maintain architectural consistency as features are added. The plan phase forces consideration of scalability trade-offs before implementation begins.
Development agencies can offer structured dev as a premium service for complex client projects. The clear phases and documentation provide transparency and reduce scope creep, allowing for fixed-price contracts with defined deliverables.
Platforms like GitHub or GitLab could integrate this pipeline as a premium feature for enterprise teams. The .dev folder structure and annotation system would become part of their collaboration tools, with automated code review integration.
Offer certification programs for development teams adopting this methodology. Include workshops, template libraries, and ongoing support for implementing the research-plan-annotate-implement workflow across organizations.
💬 Integration Tip
Start by integrating just the research and plan phases into existing sprint planning, then gradually add annotation loops for critical features before full implementation.
Scored Apr 19, 2026
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Systematic code review patterns covering security, performance, maintainability, correctness, and testing — with severity levels, structured feedback guidance, review process, and anti-patterns to avoid. Use when reviewing PRs, establishing review standards, or improving review quality.
Coding style memory that adapts to your preferences, conventions, and patterns for consistent coding.
Provides a 7-step debugging protocol plus language-specific commands to systematically identify, verify, and fix software bugs across multiple environments.
Control and operate Opencode via slash commands. Use this skill to manage sessions, select models, switch agents (plan/build), and coordinate coding through Opencode.
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions