Full Stack Master Workflow Skill

1. Capability Positioning

• Workflow Automatic Orchestration: Connect the entire lifecycle of requirement design, development, testing, quality assurance, documentation, submission, review, and release.
• Skill Aggregation: Integrate all core atomic skills (Todo Manager, Technical Planning, Backend Logic Expert, Vue Frontend Expert, Database Expert, Code Quality Auditor, Test Engineer, UI Validator, Conventional Committer).
• Reusable and Expandable: Can incorporate new scenarios (such as database migration, API changes, operation release, etc.) and support multi-project switching.
• Phased Handover/Task Assignment: Manually or script-based assignment of phase tasks to corresponding skills or specialized agents.

2. Mandatory Documentation

• Lifecycle Foundation: AGENTS.md (Security Red Lines and Identity), AI Collaboration Standards
• Planning and Tasks: Project Roadmap, To-Do Items, Project Planning Standards
• Development and Design: Development Standards, API Standards, UI Design
• Security and Quality: Security Standards, Testing Standards

3. Standard PDTFC+ 2.0 Workflow

1. P (Plan) - Requirement Analysis and Planning
   1. Read Documents: Confirm the content of

      todo.md

      and

      roadmap.md

      .
   2. Intent Extraction: Launch the interview and follow-up process to synchronize requirements.
   3. Solution Design: Use

      technical-planning

      to plan the change list, and update the status with

      todo-manager

      .
   • Skills:

     requirement-analyst

     ,

     todo-manager

     ,

     technical-planning

2. D (Do) - Development Implementation
   1. Core Implementation: Follow the Development Standards; if persistence is involved, prioritize developing entities with

      database-expert

      .
   2. Self-Inspection and Fixing: After development, eliminate Lint and type errors through

      code-quality-auditor

      .
   • Skills:

     database-expert

     ,

     backend-logic-expert

     ,

     vue-frontend-expert

     ,

     code-quality-auditor

3. A (Audit) - Code Audit
   1. Security Audit: Scan for injection, privilege escalation, and sensitive information leaks.
   2. Specification Audit: Compare with

      todo.md

      to confirm that function points are consistent with the plan.
   • Skills:

     code-quality-auditor

     ,

     security-guardian

4. C1 (Commit) - Feature Submission
   1. Atomic Commit: Use

      conventional-committer

      to perform the first commit.
5. V (Validate) - UI Validation
   1. Visual Guidelines: Verify the actual rendering effect in the browser. If automated tools fail, display screenshots to the user or request manual verification.
   • Skills:

     ui-validator

6. T (Test) - Automated Testing
   1. Targeted Testing: Write and run Vitest cases (test code must also pass the audit).
   • Skills:

     test-engineer

7. C2 (Commit) - Test Submission
   1. Final Delivery: Submit the test code.
8. F (Finish) - Task Completion
   1. Document Update: Update the status in

      todo.md

      and merge project change documents.
   • Skills:

     todo-manager

     ,

     documentation-specialist

9. Quality Inspection and Review (Test/Review)
   • Requirements: Before conducting tests, you must read the Testing Standards.
   • Tasks: Run

     pnpm lint

     ,

     pnpm typecheck

     and targeted/on-demand testing.
   • Strategy: Follow the Efficient Testing Strategy, and do not perform full-scale testing unless necessary.
   • Skills:

     quality-guardian

     ,

     test-engineer

     ,

     code-reviewer

10. Issue Fixing (Fix)
    • Goal: Eliminate all defects found in the previous stage.
    • Skills:

      nuxt-code-editor

11. Feature Submission (Commit - Phase 1)
    • Goal: Submit the business logic after passing the core quality inspection.
    • Task: Submit following the Conventional Commits specification (Chinese version).
    • Requirements: Follow Commit Scale & Atomic Changes, ensuring one commit corresponds to one Todo item and the number of files is less than 10.
    • Skills:

      conventional-committer

12. Test Enhancement (Enhance)
    • Goal: Complete test cases to improve code coverage.
    • Task: Add positive, negative, and edge scenario Vitest cases for new features.
    • Skills:

      test-engineer

13. Test Submission (Commit - Phase 2)
    • Goal: Store the enhanced test code in the repository.
    • Skills:

      conventional-committer

4. Intent Extraction Methodology

1. Gradual Progression: First lock the overall structure and goals, then delve into specific implementation details.
2. Single Point Breakthrough: Ask only one question at a time, and proceed to the next follow-up after receiving the user's answer.
3. Cycle Verification: If the user's answer is unclear, try rephrasing to confirm.
4. Intent Extraction: Analyze the "why" behind what the user wants, and provide better professional suggestions.

5. Each Sub-Skill Reference

• context-analyzer
• nuxt-code-editor
• test-engineer
• quality-guardian
• documentation-specialist
• code-reviewer
• conventional-committer
• ui-validator

6. Authoring Rules

1. Imperative & Structured
   • Standardize the usage section of each step/skill with verb + target description.
   • Prohibit lengthy nonsense and process introduction text.
2. Clear Input and Output
   • Each step must specify the input dependencies and output products (such as file paths, document links).
   • Example: Input: docs/plan/, Output: docs/design/xx.md.
3. Chainable Combination
   • Each step skill should allow independent use or serve as a local fragment of the global master call chain.
   • Some skills support multi-role collaboration (e.g., testing and documentation can be done in parallel).
4. Security Check and General Exception Handling
   • Mandatorily insert quality checkpoints such as typecheck and lint, and prohibit entering the submission/release stage without detection.
   • Clarify security levels and data protection points.
5. Internationalization and Documentation-First
   • All workflows/skills should be created with default compatibility for i18n and standard document synchronization actions.

7. Usage Example

workflow:
  - step: "需求分析"        # context-analyzer, documentation-specialist
  - step: "功能开发"        # nuxt-code-editor
  - step: "UI 验证"         # ui-validator
  - step: "质量检测"        # quality-guardian, code-reviewer
  - step: "功能提交"        # conventional-committer
  - step: "测试补充"        # test-engineer
  - step: "测试提交"        # conventional-committer