context-driven-development
在 conductor/ 目錄建立並維護 product、tech-stack、workflow 等專案 context 文件
中文翻譯
--- name: context-driven-development description: >- 在 `conductor/` 目錄中建立並維護專案 context 的成品（product.md、tech-stack.md、workflow.md、tracks.md）。 可以從零搭建新專案、從既有程式碼庫萃取 context、在實作之前驗證成品之間的一致性， 並在專案演進時同步各份文件。設定專案、建立或更新產品文件、管理 tech stack 檔案、 定義開發工作流程、追蹤工作單元、上手既有的程式碼庫，或進行專案鷹架搭建時使用。 version: 1.0.0 --- # Context-Driven Development 把 context 當成跟程式碼並列、被管理的成品來實作和維護的指南，透過結構化的專案文件，讓 AI 的互動前後一致，也讓團隊保持一致。 ## 何時使用這個 Skill - 用 Conductor 設定新專案 - 了解各個 context 成品之間的關係 - 在 AI 輔助的開發 session 之間維持一致性 - 讓團隊成員上手既有的 Conductor 專案 - 決定何時該更新 context 文件 - 管理 greenfield 和 brownfield 專案的 context ## 詳細模式與實作範例 詳細的模式文件放在 `references/details.md`。上面的導覽層不夠用時，再讀那個檔案。 ## 最佳實務 1. **先讀 context**：開始工作前，一定要先讀相關的成品 2. **小幅更新**：對 context 做漸進式的修改，不要大幅重寫 3. **連結決策**：做實作選擇時，要引用 context 4. **替 context 做版本控制**：把 context 的變更跟程式碼的變更一起 commit 5. **審查 context**：把 context 成品的審查納入 code review 6. **定期驗證**：做重大工作之前，先跑 context 驗證檢查清單 7. **溝通變更**：context 成品有重大變動時，通知團隊 8. **保存歷史**：用 git 追蹤 context 隨時間的演進 9. **質疑過時**：如果 context 感覺不對，就去調查並更新 10. **保持可執行**：每個 context 項目都應該能影響某個決定或行為
英文原文
--- name: context-driven-development description: >- Creates and maintains project context artifacts (product.md, tech-stack.md, workflow.md, tracks.md) in a `conductor/` directory. Scaffolds new projects from scratch, extracts context from existing codebases, validates artifact consistency before implementation, and synchronizes documents as the project evolves. Use when setting up a project, creating or updating product docs, managing a tech stack file, defining development workflows, tracking work units, onboarding to an existing codebase, or running project scaffolding. version: 1.0.0 --- # Context-Driven Development Guide for implementing and maintaining context as a managed artifact alongside code, enabling consistent AI interactions and team alignment through structured project documentation. ## When to Use This Skill - Setting up new projects with Conductor - Understanding the relationship between context artifacts - Maintaining consistency across AI-assisted development sessions - Onboarding team members to an existing Conductor project - Deciding when to update context documents - Managing greenfield vs brownfield project contexts ## Detailed patterns and worked examples Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient. ## Best Practices 1. **Read context first**: Always read relevant artifacts before starting work 2. **Small updates**: Make incremental context changes, not massive rewrites 3. **Link decisions**: Reference context when making implementation choices 4. **Version context**: Commit context changes alongside code changes 5. **Review context**: Include context artifact reviews in code reviews 6. **Validate regularly**: Run context validation checklist before major work 7. **Communicate changes**: Notify team when context artifacts change significantly 8. **Preserve history**: Use git to track context evolution over time 9. **Question staleness**: If context feels wrong, investigate and update 10. **Keep it actionable**: Every context item should inform a decision or behavior