@flydocs/cli 0.6.0-alpha.3 → 0.6.0-alpha.30

package/template/.flydocs/config.json

@@ -1,18 +1,17 @@
 {
-  "version": "0.6.0-alpha.3",
+  "version": "0.6.0-alpha.30",
   "sourceRepo": "github.com/plastrlab/flydocs-core",
   "tier": "local",
   "setupComplete": false,
+  "onboardComplete": false,
+  "workspaceId": null,
   "paths": {
     "content": "flydocs"
   },
-  "provider": {
-    "type": null,
-    "teamId": null
-  },
   "workspace": {
     "activeProjects": [],
     "defaultMilestoneId": null,
+    "repoSlug": null,
     "product": {
       "name": null,
       "labelIds": [],
@@ -21,7 +20,7 @@
     }
   },
   "issueLabels": {
-    "_note": "Run /flydocs-setup to populate these from your Linear team",
+    "_note": "Run /flydocs-setup to populate these from your workspace",
     "category": {
       "feature": null,
       "bug": null,
@@ -50,18 +49,6 @@
     "installed": [],
     "custom": []
   },
-  "statusMapping": {
-    "BACKLOG": "Backlog",
-    "READY": "Todo",
-    "IMPLEMENTING": "In Progress",
-    "BLOCKED": "Blocked",
-    "REVIEW": "In Review",
-    "TESTING": "QA",
-    "COMPLETE": "Done",
-    "ARCHIVED": "Archived",
-    "CANCELED": "Canceled",
-    "DUPLICATE": "Duplicate"
-  },
   "designSystem": null,
   "aiLabor": {
     "enabled": false,

package/template/.flydocs/templates/README.md

@@ -1,31 +1,33 @@
 # Issue Templates
 
-This folder contains templates for creating and refining Linear issues. Each template includes agent instructions to ensure consistent, high-quality issue structure.
+This folder contains templates for creating and refining issues. Each template includes agent instructions to ensure consistent, high-quality issue structure.
 
 ## Template Usage
 
 **Agents use these templates when:**
+
 - Creating new issues via `/capture`
 - Refining issues via `/refine`
 - Triaging quick captures with `triage` label
 
-**Humans use `quick-capture.md` in Linear** as the default template for fast idea/bug capture.
+**Humans use `quick-capture.md` in their issue tracker** as the default template for fast idea/bug capture.
 
 ## Available Templates
 
-| Template | Purpose | When to Use |
-|----------|---------|-------------|
-| `feature.md` | New functionality | Building something new with user story |
-| `bug.md` | Fix defects | Something is broken |
-| `chore.md` | Maintenance/cleanup | Refactoring, polish, improvements |
-| `idea.md` | Capture concepts | Rough ideas for future exploration |
-| `quick-capture.md` | Fast capture | Human entry in Linear (default template) |
+| Template           | Purpose             | When to Use                                     |
+| ------------------ | ------------------- | ----------------------------------------------- |
+| `feature.md`       | New functionality   | Building something new with user story          |
+| `bug.md`           | Fix defects         | Something is broken                             |
+| `chore.md`         | Maintenance/cleanup | Refactoring, polish, improvements               |
+| `idea.md`          | Capture concepts    | Rough ideas for future exploration              |
+| `quick-capture.md` | Fast capture        | Human entry in issue tracker (default template) |
 
 ## Agent Instructions
 
-Each template contains `<!-- AGENT: ... -->` comments that guide the AI when filling out sections. These instructions are removed from the final issue in Linear.
+Each template contains `<!-- AGENT: ... -->` comments that guide the AI when filling out sections. These instructions are removed from the final issue in your provider.
 
 **Key principles:**
+
 1. Fill all `[bracketed]` sections with specific content
 2. Don't remove sections - mark as "N/A" if not applicable
 3. Be specific in acceptance criteria (testable, measurable)
@@ -35,12 +37,9 @@ Each template contains `<!-- AGENT: ... -->` comments that guide the AI when fil
 ## Template Evolution
 
 Update these templates as your workflow evolves:
+
 - Add sections that are consistently needed
 - Remove sections that are never used
 - Improve agent instructions based on what works
 
 Changes here apply to all future issues.
-
-
-
-

package/template/.flydocs/templates/bug.md

@@ -1,166 +1,30 @@
-<!-- AGENT INSTRUCTIONS
-When creating or refining a bug issue:
+<!-- AGENT: Use this template when creating bug issues. Fill all [bracketed] sections. -->
 
-1. CONTEXT SECTION:
-   - Capture when/how the bug was discovered
-   - Assess user impact (how many affected, how severe)
-   - Note frequency (always, sometimes, specific conditions)
+## What
 
-2. BUG DESCRIPTION:
-   - Expected vs Actual must be crystal clear
-   - Steps to reproduce must be detailed enough for anyone to follow
-   - Include specific data conditions if relevant
-   - Note environment details (browser, OS, user role)
+[One sentence describing the bug]
 
-3. ACCEPTANCE CRITERIA:
-   - "Fix Verification" should mirror the reproduction steps
-   - Include regression concerns (what else might break)
-   - Tests section should include regression test requirement
+## Expected Behavior
 
-4. TECHNICAL NOTES:
-   - Start with hypothesis if cause unknown
-   - Update "Confirmed Cause" after investigation
-   - Include specific file/function where bug exists
-   - Assess risk of the fix
+[What should happen]
 
-5. SEVERITY GUIDANCE:
-   - Critical: System unusable, data loss, security issue
-   - High: Major feature broken, no workaround
-   - Medium: Feature impaired but workaround exists
-   - Low: Minor issue, cosmetic, edge case
+## Actual Behavior
 
-Remove these instructions when creating the final issue.
--->
+[What actually happens]
 
-## Context
-
-**When Discovered:** [Date or event when bug was found]
-**Discovered By:** [User, developer, automated test, etc.]
-**Impact:** [How this affects users - be specific about scope]
-**Frequency:** [Always | Sometimes | Rarely | Under specific conditions]
-
-[Additional context about the bug]
-
----
-
-## Bug Description
-
-### Expected Behavior
-[Describe what SHOULD happen - the correct behavior]
-
-### Actual Behavior
-[Describe what ACTUALLY happens - the broken behavior]
-
-### Steps to Reproduce
-1. [First action - be specific]
-2. [Second action - include any data/conditions needed]
-3. [Third action]
-4. [Observe the bug]
-
-### Environment
-- **Browser/Platform:** [Chrome, Safari, Mobile, etc.]
-- **OS:** [macOS, Windows, iOS, Android, etc.]
-- **User Role:** [Which user type experiences this]
-- **Data Conditions:** [Specific data state that triggers bug]
-
-### Screenshots/Evidence
-<!-- Add as attachments -->
+## Steps to Reproduce
 
----
+1. [Step 1]
+2. [Step 2]
+3. [Step 3]
 
 ## Acceptance Criteria
 
-### Fix Verification
-- [ ] Bug no longer reproducible using original steps
-- [ ] Expected behavior now works correctly
-- [ ] Fix doesn't break related functionality
-- [ ] No new error messages or console errors
-
-### Tests
-- [ ] Regression test added to prevent recurrence
-- [ ] Related edge cases tested
-- [ ] All tests passing
-
-### Documentation
-- [ ] Root cause documented (if significant pattern)
-- [ ] Prevention notes added to knowledge base (if applicable)
-- [ ] N/A - No significant documentation needed
-
----
-
-## Technical Notes
-
-### Root Cause Analysis
-**Hypothesis:** [What you think is causing the bug]
-
-**Investigation Findings:**
-- [Finding 1 from debugging]
-- [Finding 2 from debugging]
-
-**Confirmed Cause:** [What's actually wrong - file, function, logic error]
-
-### Fix Approach
-[Describe the fix strategy - what needs to change]
-
-**Files to Modify:**
-- `path/to/file.tsx` - [What needs to change]
-
-**Risk Assessment:**
-- **Regression Risk:** Low | Medium | High
-- **Testing Required:** [What needs to be tested]
-
----
-
-## Dependencies
-
-**Related Systems:**
-- [System or feature where bug occurs]
-
-**Blocks:**
-- [Work that can't proceed until bug is fixed]
-- OR: Nothing blocked
-
-**Related Bugs:**
-- [Link to related bug if applicable]
-- OR: No related issues
-
----
-
-## AI Effort Estimate
-<!-- 
-AGENT: Fill this section during /refine using the flydocs-estimates skill.
-See .claude/skills/flydocs-estimates/SKILL.md for calculation details.
-Update Actuals section during /close for calibration.
--->
-
-### Sizing Factors
-
-| Factor | Value | Multiplier |
-|--------|-------|------------|
-| **Task Type** | bug | base: 20k |
-| **Scope** | [S/M/L/XL] | ×[0.5/1.0/2.0/4.0] |
-| **Novelty** | [existing/partial/greenfield] | ×[0.7/1.2/2.0] |
-| **Clarity** | [defined/discovery/exploratory] | ×[0.8/1.5/2.5] |
-| **Codebase** | [simple/moderate/complex] | ×[0.8/1.0/1.5] |
-
-### Estimate
-
-**Provider**: [Claude Sonnet 4]  
-**Calculated Tokens**: ~[X]k  
-**Confidence**: ±[40-60]%  
-**Token Range**: [low]k - [high]k  
-**Cost Range**: $[low] - $[high]
-
-### Actuals (fill on /close)
-**Actual Tokens**: [fill after completion]  
-**Variance**: [+/-X]% [under/over estimate]  
-**Notes**: [what drove variance - investigation time, fix complexity, retries]
-
----
-
-_Reported: YYYY-MM-DD_
-
-
-
+- [ ] Bug is fixed and original behavior restored
+- [ ] [Additional verification criteria]
 
+## Context
 
+- **Frequency:** [Always / Sometimes / Rare]
+- **Impact:** [Blocking / Degraded / Cosmetic]
+- **Environment:** [Where it occurs — browser, OS, tier]

package/template/.flydocs/templates/chore.md

@@ -1,110 +1,22 @@
-<!-- AGENT INSTRUCTIONS
-When creating or refining a chore issue:
+<!-- AGENT: Use this template when creating chore issues. Fill all [bracketed] sections. -->
 
-1. CONTEXT SECTION:
-   - Explain the value (cleaner code, better UX, faster performance)
-   - Be specific about scope to prevent scope creep
-   - Mark as "Ongoing" if this is iterative work
+## What
 
-2. TASK LIST:
-   - Be specific and actionable
-   - Add tasks as you discover them during work
-   - Move tasks to "Out of Scope" if they're too big
-   - Tasks should be completable in one session
+[One sentence describing the task]
 
-3. ACCEPTANCE CRITERIA:
-   - Focus on completion and quality
-   - Mark documentation as N/A if no new patterns
-   - Mark tests as N/A if no behavior changes
+## Why
 
-4. COMPLETION CRITERIA:
-   - "Done when" should be clear stopping point
-   - If scope keeps growing, suggest splitting into multiple chores
-
-5. WORKFLOW:
-   - Chores often skip formal review/QA
-   - Use simplified flow: Backlog → In Progress → Done
-   - Use full flow only for significant refactors
-
-Remove these instructions when creating the final issue.
--->
-
-## Context
-
-**Why This Matters:**
-[Explanation of the value - cleaner code, better UX, faster performance, etc.]
-
-**Scope:**
-[What areas/pages/features does this touch? Be specific enough to stay focused.]
-
-**Type:** Ongoing | One-time
-
----
-
-## Task List
-
-### Initial Tasks
-- [ ] [Task 1 - be specific]
-- [ ] [Task 2 - be specific]
-- [ ] [Task 3 - be specific]
-
-### Added During Work
-<!-- Add new tasks discovered while working -->
-
-### Out of Scope
-<!-- Tasks that don't fit - might become new issues -->
-- [Task that's too big or different focus]
-
----
+[Why this maintenance/cleanup is needed now]
 
 ## Acceptance Criteria
 
-### Completion
-- [ ] All initial tasks completed (or moved to out of scope)
-- [ ] Code quality acceptable
-- [ ] No regressions introduced
-
-### Tests
-- [ ] Tests updated if behavior changed
-- [ ] All tests passing
-- [ ] N/A - No behavior changes
+- [ ] [Specific, testable criterion 1]
+- [ ] [Specific, testable criterion 2]
 
-### Documentation
-- [ ] Patterns documented (if new approach discovered)
-- [ ] N/A - No significant documentation needed
+## Scope
 
----
+[What's included and what's explicitly excluded]
 
 ## Technical Notes
 
-### Approach
-[How you'll tackle this work]
-
-### Files to Touch
-- `path/to/file.tsx` - [What changes]
-
-### Risk Assessment
-- **Regression Risk:** Low | Medium | High
-- **Related Areas:** [What else might be affected]
-
----
-
-## Completion Criteria
-
-**This chore is done when:**
-- [ ] [Completion criterion 1]
-- [ ] [Completion criterion 2]
-- [ ] No obvious improvements remaining in scope
-
-**Signs this needs to be split:**
-- Work has been ongoing for 3+ weeks
-- Scope has grown significantly
-- New tasks are unrelated to original purpose
-
----
-
-_Created: YYYY-MM-DD_
-
-
-
-
+[Approach, risks, or migration steps — remove if not applicable]

package/template/.flydocs/templates/feature.md

@@ -1,173 +1,27 @@
-<!-- AGENT INSTRUCTIONS
-When creating or refining a feature issue:
+<!-- AGENT: Use this template when creating feature issues. Fill all [bracketed] sections. -->
 
-1. CONTEXT SECTION:
-   - Explain the problem being solved, not just the solution
-   - Include business value or user impact
-   - Reference project goals from {content-folder}/context/overview.md if relevant
+## What
 
-2. USER STORY:
-   - Must follow "As a... I want... So that..." format
-   - Be specific about the user role (not just "user")
-   - Benefit should be concrete and measurable
-   - Include an example scenario for clarity
+[One sentence describing the feature]
 
-3. ACCEPTANCE CRITERIA:
-   - Each criterion must be testable and specific
-   - Use checkboxes for tracking completion
-   - Include error handling scenarios
-   - "Must Have" = required for completion
-   - "Should Have" = nice to have, not blocking
-   - "Won't Have" = explicitly out of scope
+## Why
 
-4. TECHNICAL NOTES:
-   - Reference patterns from {content-folder}/context/stack.md
-   - List specific components/files to create or modify
-   - Include data model changes if applicable
-   - Note any API changes needed
-
-5. DEPENDENCIES:
-   - List issues that must be completed first
-   - Note what future work this enables
-
-Remove these instructions when creating the final issue.
--->
-
-## Context
-
-[Problem description - what user pain or business need does this address?]
-
-**Current Issues:**
-- [Issue or limitation 1]
-- [Issue or limitation 2]
-
----
+[Problem this solves or opportunity it creates]
 
 ## User Story
 
-**As a** [specific user role]
-**I want to** [specific goal or action]
-**So that** [concrete benefit or outcome]
-
-**Example Scenario:**
-[Real-world scenario where this feature would be used]
-
----
+As a [role], I want to [action] so that [benefit].
 
 ## Acceptance Criteria
 
-### Must Have
-- [ ] [Specific, measurable criterion 1]
-- [ ] [User can perform X action and see Y result]
-- [ ] [System behaves correctly when Z happens]
-- [ ] [Error handling: System shows helpful message when...]
-
-### Should Have
-- [ ] [Nice-to-have enhancement]
-
-### Won't Have (Out of Scope)
-- [Explicitly excluded functionality]
-
-### Tests
-- [ ] Tests written for core functionality
-- [ ] Edge cases and error scenarios covered
-- [ ] All tests passing
-
-### Documentation
-- [ ] Code documented (comments on complex logic)
-- [ ] Knowledge base updated (if significant decisions/patterns)
-- [ ] Context files updated (if architecture changes)
-- [ ] N/A - No significant documentation needed
-
----
+- [ ] [Specific, testable criterion 1]
+- [ ] [Specific, testable criterion 2]
+- [ ] [Specific, testable criterion 3]
 
 ## Technical Notes
 
-### Implementation Approach
-[High-level description of how this will be built]
-
-**Key Technical Decisions:**
-1. [Decision 1 and rationale]
-2. [Decision 2 and rationale]
-
-### Components Needed
-**New:**
-- `ComponentName` - [What it does]
-
-**Modify:**
-- `ExistingComponent` - [What changes needed]
-
-### Data Model
-```typescript
-// Schema changes if any
-// OR: No data model changes required
-```
-
-### API Endpoints
-- `POST /api/endpoint` - [Description]
-- OR: No new endpoints required
-
----
-
-## Dependencies
-
-**Required Before Starting:**
-- [Feature or system that must exist first]
-- OR: No dependencies - can start immediately
-
-**Enables Future Work:**
-- [Feature that depends on this being complete]
-
----
-
-## Design Reference
-<!-- Add Figma links as attachments -->
-
----
-
-## AI Effort Estimate
-<!-- 
-AGENT: Fill this section during /refine using the flydocs-estimates skill.
-See .claude/skills/flydocs-estimates/SKILL.md for calculation details.
-Update Actuals section during /close for calibration.
--->
-
-### Sizing Factors
-
-| Factor | Value | Multiplier |
-|--------|-------|------------|
-| **Task Type** | feature | base: 40k |
-| **Scope** | [S/M/L/XL] | ×[0.5/1.0/2.0/4.0] |
-| **Novelty** | [existing/partial/greenfield] | ×[0.7/1.2/2.0] |
-| **Clarity** | [defined/discovery/exploratory] | ×[0.8/1.5/2.5] |
-| **Codebase** | [simple/moderate/complex] | ×[0.8/1.0/1.5] |
-
-### Estimate
-
-**Provider**: [Claude Sonnet 4]  
-**Calculated Tokens**: ~[X]k  
-**Confidence**: ±[40-60]%  
-**Token Range**: [low]k - [high]k  
-**Cost Range**: $[low] - $[high]
-
-### Approach Comparison
-
-| Approach | Est. Cost | Est. Time | Recommendation |
-|----------|-----------|-----------|----------------|
-| **Full AI** | $[X] | [X] hrs | [When to use] |
-| **AI-Assisted** | $[X] + [X]hrs | [X] hrs | [When to use] |
-| **Human-Led** | $[X] (review) | [X] hrs | [When to use] |
-
-### Actuals (fill on /close)
-**Actual Tokens**: [fill after completion]  
-**Variance**: [+/-X]% [under/over estimate]  
-**Notes**: [what drove variance - blockers, scope changes, retries]
-
----
-
-_Created: YYYY-MM-DD_
-
-
-
+[Implementation approach, constraints, or dependencies — remove if not applicable]
 
+## Out of Scope
 
+[Explicitly list what this does NOT include — remove if not applicable]