@flydocs/cli 0.6.0-alpha.13 → 0.6.0-alpha.20

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

@@ -1,110 +0,0 @@
-<!-- AGENT INSTRUCTIONS
-When creating or refining a chore issue:
-
-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
-
-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
-
-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
-
-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]
-
----
-
-## 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
-
-### Documentation
-- [ ] Patterns documented (if new approach discovered)
-- [ ] N/A - No significant documentation needed
-
----
-
-## 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_
-
-
-
-

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

@@ -1,173 +0,0 @@
-<!-- AGENT INSTRUCTIONS
-When creating or refining a feature issue:
-
-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
-
-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
-
-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
-
-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]
-
----
-
-## 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]
-
----
-
-## 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
-
----
-
-## 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_
-
-
-
-
-

package/template/.flydocs/templates/idea.md

@@ -1,122 +0,0 @@
-<!-- AGENT INSTRUCTIONS
-When creating or refining an idea issue:
-
-1. SKETCH SECTION:
-   - Keep it light - this is brainstorming
-   - What/Why/How should each be one sentence
-   - Details can be rough notes
-
-2. POTENTIAL VALUE:
-   - Think about user benefit first
-   - Business value second
-   - Be honest about impact uncertainty
-
-3. QUESTIONS TO ANSWER:
-   - Capture what you don't know
-   - These become research tasks before refinement
-   - Include feasibility, effort, and value questions
-
-4. COMPLEXITY:
-   - If XL or larger, note how to break it down
-   - Ideas often seem smaller until investigated
-
-5. STATUS TRACKING:
-   - Ideas follow: Captured → Researched → Validated → Refined or Declined
-   - "Refined" means it became a full feature issue
-   - "Declined" with reason is valuable documentation
-
-6. CONVERSION:
-   - When idea is validated, create feature issue
-   - Link the feature issue in "Refined" status
-
-Remove these instructions when creating the final issue.
--->
-
-## Sketch
-
-**Quick Description:**
-- **What:** [One sentence - what is this?]
-- **Why:** [One sentence - why might this be valuable?]
-- **How:** [One sentence - rough idea of how it might work]
-
-**Details:**
-[Additional thoughts, context, inspiration, related ideas]
-
----
-
-## Potential Value
-
-**For Users:**
-- [Benefit 1]
-- [Benefit 2]
-
-**For Business/Product:**
-- [Value 1]
-- [Value 2]
-
-**Estimated Impact:** 🔥 High | 📊 Medium | 💡 Low | ❓ Unknown
-
----
-
-## Questions to Answer
-
-**Unknowns:**
-- [ ] What needs research or investigation?
-- [ ] What's the technical feasibility?
-- [ ] What's the rough effort estimate?
-- [ ] Does this already exist elsewhere?
-
-**Dependencies:**
-- [ ] Does this depend on other work?
-- [ ] Are there technical constraints?
-
-**Risks:**
-- [ ] What could go wrong?
-
----
-
-## Rough Complexity
-
-**Complexity:** XS | S | M | L | XL | ❓ Unknown
-
-**If XL or larger:**
-[How could this be broken into smaller features?]
-
----
-
-## Next Steps
-
-**To Validate This Idea:**
-1. [Research step 1]
-2. [User validation needed]
-3. [Technical spike or prototype]
-
-**To Turn Into a Feature:**
-1. [ ] Answer the questions above
-2. [ ] Define clear user story and acceptance criteria
-3. [ ] Get stakeholder buy-in
-4. [ ] Create feature issue with full template
-
----
-
-## Status Tracking
-
-- [ ] **Captured** - Idea written down ✅
-- [ ] **Researched** - Questions answered, feasibility checked
-- [ ] **Validated** - Worth pursuing
-- [ ] **Refined** - Converted to full feature issue
-- [ ] **Declined** - Decided not to pursue
-
-**If Declined:**
-- **Reason:** [Why we decided not to do this]
-
-**If Refined:**
-- **New Issue:** [Link to feature issue created from this idea]
-
----
-
-_Captured: YYYY-MM-DD_
-
-
-
-